Different unique identifiers used in CELLAR database.

The CELEX number is both a unique document identifier and a classification code, regardless of language. It is used as the basis for cross-referencing of documents in the database as well as for implementing hypertext links.

CELEX number is composed as follows:

SyyyyT(T)nnn(n)

S 1 character for the sector (see list below)
yyyy 4 digits for the year (usually the year of adoption)
T(T) 1 or 2 characters for the document type (see list below)
nnnn 4 digits (usually) for the document number

For example, document 32014R1338 is:

a sector 3 document (secondary legislation) 32014R1338
from 2014 32014R1338
a regulation 32014R1338
published in the OJ under number 1338 32014R1338

Some of the above mentioned partial information is contained in the following metadata fields:

Document type sector (DTS)
Document type year (DTA)
Document type type (DTT)
Document natural number (DT_NUM)

In some instances composed or non-standardised numbers are attributed (especially sector C documents and National implementing measures; but also treaties or parliamentary questions). There is a specific format of CELEX numbers for corrigenda.

Such documents as daily Euro exchange rates, information (OJ-C II) or announcements (OJ-C V) related to concentrations, minutes of the sitting (OJ-C IV) and other notices published in the C series (under OJ-C IV) are covered by sector C; their CELEX numbers are attributed automatically.

CELEX number is attributed by OP or the legal analysis contractor (based on the analysis) on a daily basis to all acts published in L series of the Official Journal and to some of those published in C series of the Official Journal.

Any change of an already attributed CELEX number must be approved by the Publications Office.

For some specific collections of documents, CELEX number is attributed by the author or institution responsible (e.g. EU case law – documents from the Court of justice of the European Union).

<cdm:resource_legal_id_celex rdf:datatype="http://www.w3.org/2001/XMLSchema#string">32015D0046</cdm:resource_legal_id_celex>

The year attributed to the document (internal number or ppf number).

General rule: year referenced in the document. It is usually based on the natural number of document, on the internal number of document attributed by author, or on the date of publication.

The CELEX year represents:

for sector 1: year of signature of the treaty ( for consolidated texts the year of the publication),
for sector 2: the year of publication of the agreement (for old documents the year of the signature),
for sectors 3 and 4: the year of the natural or internal document number,
for sector 5: the year of the natural or internal document number,
for sector 6: the year the case was lodged,
for sector 7: the year of adoption of corresponding directive,
for sector 9: the year the question was introduced.

<cdm:resource_legal_year rdf:datatype="http://www.w3.org/2001/XMLSchema#gYear">2014</cdm:resource_legal_year>

A sequential number representing the original reference number of the act.

In some instances composed or non-standardised numbers are attributed (e.g. treaties).

The sequential number is usually present in the natural number of document (e.g. regulations) or on its internal number attributed by the author (e.g. COM documents). If any of those numbers is not available, the CELEX natural number might be based on the date of publication (international agreements).

The date of publication is derived from the publication reference.

Numbers in parentheses (called "splits" – e.g. (01), (02), …) may be added to avoid double application (if the CELEX number of several similar documents is based on the same date of publication; for several Court decisions on the same case for several documentary units for a preparatory document).

For a corrigendum an “R” is added to the four digits (see CELEX type corrigendum).

<cdm:resource_legal_number_natural_celex rdf:datatype="http://www.w3.org/2001/XMLSchema#positiveInteger">0556</cdm:resource_legal_number_natural_celex>

This refers to a specific sector (collection) of documents as indicated in the CELEX number (it is the first number in the celex number).

Documents in EUR-Lex fall into one of 12 sectors.
1 Treaties
2 International agreements
3 Legal acts
4 Complementary legislation
5 Preparatory documents
6 EU case law
7 National transposition
8 References to national case-law concerning EU law
9 Parliamentary questions
0 Consolidated texts
C Other documents published in the Official Journal C series
E EFTA documents

<j.0:resource_legal_id_sector rdf:datatype="http://www.w3.org/2001/XMLSchema#string">2</j.0:resource_legal_id_sector>

This one or two letters code refers to a specific type of document as indicated in the CELEX number.

In some cases, this metadata is related to another metadata field Form (FM), Author (AU) Author.
Celex type of sector 1 documents refers to a specific treaty.

<cdm:resource_legal_type rdf:datatype="http://www.w3.org/2001/XMLSchema#string">D</cdm:resource_legal_type>

This field indicates if the document is a corrigendum. The number inserted indicates the serial number of corrigendum. It is then displayed in the celex number of corrigendum as "split" number in the brackets.

If a document is a corrigendum, it is usually indicated in the title of document. Also the text of the document must be analysed.

A corrigendum may affect one or more language versions of a document.

The sequential number of corrigendum must be attributed only after analysing the CELEX numbers of previously published corrigenda related to the same act.

<cdm:resource_legal_number_corrigendum rdf:datatype="http://www.w3.org/2001/XMLSchema#positiveInteger">1</cdm:resource_legal_number_corrigendum>

Identifier of the Official Journal in which was the document published.

The OJ identifier contains several parts:
- collection OJL or OJC
- year of the OJ
- number of the OJ

<j.0:resource_legal_published_in_official-journal rdf:resource="http://publications.europa.eu/resource/oj/JOL_2010_276_R"/>

Properties describing different dates.

Annotation specifying date metadata.

The translation tables should be used as follows:

DD, NF: fd_365,
IF: fd_335,
EV: fd_330,
TP: fd_361,
DH: fd_340,
DL: fd_335,
RP: fd_350,
SG: at:place, at:country

<annot:comment_on_date>{DATSIG|http://publications.europa.eu/resource/authority/fd_365/DATSIG}</annot:comment_on_date>

<annot:comment_on_date>{V|http://publications.europa.eu/resource/authority/fd_335/V} {ART|http://publications.europa.eu/resource/authority/fd_335/ART} 22</annot:comment_on_date>

2019/06/25: Differences between ann:comment_on_date and ann:type_of_date are not fully clear

Annotation specifying date metadata.

The translation tables should be used as follows:

IF: fd_335,
RP: fd_350

<annot:type_of_date>{EV|http://publications.europa.eu/resource/authority/fd_335/EV}</annot:type_of_date>

2019/06/25: Differences between ann:comment_on_date and ann:type_of_date are not fully clear

This field contains the date of vote on decisions or resolutions of the European Parliament or on committees (EESC/CoR) opinions.

The date has format YYYY-MM-DD.

The date of vote is indicated in the document or in OJ.

<cdm:resource_legal_date_vote rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2009-03-25</cdm:resource_legal_date_vote>

2015/10/14: Date of vote in sector 2 – resolutions, declarations: Joint Parliamentary Assembly of the Partnership Agreement concluded between the members of the African, Caribbean and Pacific group of States, of the one part, and the European Community and its Member States, of the other part - Resolution on racism, racial discrimination, xenophobia and related intolerance (ACP-EU 3549/03/fin) 22003P0926(14)

Court of Justice of the European Union documents: the field indicates when the document was lodged with the Registrar of the EU Court of Justice (or EFTA Court).

Committee of Regions, European Economic and Social Committee: Date on which a proposal is submitted for consultation.

The date has format YYYY-MM-DD.

EU case law documents (sector 6): analysis provided by Court of Justice of the European Union.

Documents from sector 5 – the date as indicated in the text:

On 3 July 2013, the Commission decided to consult the European Economic and Social Committee, under Article 304 of the Treaty on the Functioning of the European Union, on (…)

<cdm:resource_legal_date_request_opinion rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2013-02-19</cdm:resource_legal_date_request_opinion>

31/10/2019: Clarify the description & methodology. How is this date treated in IMMC?

It is a date when the act enters into force or becomes operative.

The date has the format YYYY-MM-DD or 1001-01-01 (a fictional date for documents that take effect by notification; to be changed in a factual date if/when the notification date is known).

The date of effect is also used as an indicator for the production of the Directory of legislation in force and of the Directory of preparatory acts.

The date of effect must be followed by an annotation specifying the nature of the date as shown below (annot:type_of date):

• Entry into force (for all acts entering into force – art. 297 of TFEU)
• Takes effect (for all acts taking effect – art. 297 of TFEU)
• Takes partial effect
• Application (if the date of application is different as the date when the act enters into force/takes effect (see 32014R0376)
• Partial application (for example "However, Article 8 shall apply from…" see 32015R0104)
• Provisional application

There might be also another annotation annot:comment_on_date indicating how the date of effect is counted and which part of the document refers to the date of effect.

Example 1:
<rdf:Description rdf:nodeID="A1">
<owl:annotatedSource rdf:resource="http://publications.europa.eu/resource/celex/22015A0319%2801%29"/>
<owl:annotatedProperty rdf:resource="http://publications.europa.eu/ontology/cdm#resource_legal_date_entry-into-force"/>
<owl:annotatedTarget rdf:datatype="http://www.w3.org/2001/XMLSchema#date">1001-01-01</owl:annotatedTarget>
<annot:type_of_date>{EV|http://publications.europa.eu/resource/authority/fd_335/EV}</annot:type_of_date>
<annot:comment_on_date>{V|http://publications.europa.eu/resource/authority/fd_335/V} {ART|http://publications.europa.eu/resource/authority/fd_335/ART} 22</annot:comment_on_date>
<annot:build_info>cdm:CDM_2.1.7 tdm:1523 xslt:3945 saxon:9.0.0.1J JVM:1.6.0_29 metaconvJar:1.2.0 builddate:27/03/2015 17:57:38</annot:build_info>
<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Axiom"/>
</rdf:Description>

Example 2:
<annot:comment_on_date>{DATPUB|http://publications.europa.eu/resource/authority/fd_335/DATPUB} +20 {V|http://publications.europa.eu/resource/authority/fd_335/V} {ART|http://publications.europa.eu/resource/authority/fd_335/ART} 3</annot:comment_on_date>

The field can include several dates, when the date of entry into force and the date of application are not the same. Each date is accompanied by an indication of the type.

The period of effect of an acts starts at 00.00 on the date indicated. The reference to the date of effect is indicated in the act.

Entry into force vs Taking effect
General rules for the date of effect are indicated in article 297 of the Treaty on the Functioning of the European Union (twentieth day following the day of publication).

Article 297
(ex Article 254 TEC)

1. Legislative acts adopted under the ordinary legislative procedure shall be signed by the President of the European Parliament and by the President of the Council.

Legislative acts adopted under a special legislative procedure shall be signed by the President of the institution which adopted them.

Legislative acts shall be published in the Official Journal of the European Union. They shall enter into force on the date specified in them or, in the absence thereof, on the twentieth day following that of their publication.

2. Non-legislative acts adopted in the form of regulations, directives or decisions, when the latter do not specify to whom they are addressed, shall be signed by the President of the institution which adopted them.

Regulations and directives which are addressed to all Member States, as well as decisions which do not specify to whom they are addressed, shall be published in the Official Journal of the European Union. They shall enter into force on the date specified in them or, in the absence thereof, on the twentieth day following that of their publication.

Other directives, and decisions which specify to whom they are addressed, shall be notified to those to whom they are addressed and shall take effect upon such notification.

Please note differences between acts entering into force and acts taking effect (based on the provisions of TFEU article 297 quoted above).

I. Legislative acts – TFEU article 297(1): enter into force
- ordinary legislative procedure
- special legislative procedure
Display on EUR-Lex: Date of effect: dd/mm/yyyy; Entry into force

II. Non-legislative acts – TFEU article 297(2):
1. Regulations: enter into force

2. Directives:
(a) Directives addressed to all Member States: enter into force
(b) Other directives: take effect (+ Date of effect (IF) is linked to the Date of notification (NF))

3. Decisions:
(a) Decisions which do not specify to whom they are addressed: enter into force
(b) Decisions which do specify to whom they are addressed (incl those addresed to all Member States): take effect (+ Date of effect (IF) is linked to the Date of notification (NF))

Display on EUR-Lex – cases 1, 2(a) and 3(a):
Date of effect: dd/mm/yyyy; Entry into force

Display on EUR-Lex – cases 2(b) and 3(b):
Date of effect: dd/mm/yyyy; Takes effect

Note: Some non-legislative Council acts (decisions or directives which specify to whom they are addressed; but also Decisions of representatives of the governments of the Member States or recommendations) may contain a date of notification not linked to the date of enter into force/date of effect (which is indicated in the act). In this case the Date of notification (NF) will be created after receiving it from the relevant service. The Date of effect (IF) field (with the annotation Entry into force (e.g. 32015D2358) or Takes effect (e.g. 32015D0954), according to the text) will not be impacted by this change (for more details see Date of effect (IF)).

Entry into force vs Application
Please note also differences between enter into force and application. See the example below.

Text of the regulation:

Article 5

This Regulation shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union.

It shall apply from 1 April 2015.

Information displayed on the EUR-Lex:

Date of effect: 04/02/2015; Entry into force Date pub. +20 See Art 5
Date of effect: 01/04/2015; Application See Art 5

Date of effect and date of notification
If the date of effect is not known and depends on the date of notification, insert 01-01-1001 + Takes effect + Date of notification:

Date of document: 14/08/2014
Date of effect: 01/01/1001; Takes effect Date notif.

If acts with date of effect which is not yet known amends other acts (MS relation to be created), annotation start_of_validity to this relation should also contain the fictional date 01-01-1001. This will be changed to a real date together with IF date.

Special cases
a) In some special cases, the date of effect can be earlier as the date of document (retroactive effect).

b) The "date of effect" field of an agreement with a third country that has been adopted by a regulation (and published together with this regulation in OJ) will show the same date as that of the adopting regulation.

c) Acts only repealing another act – they are usually effective as indicated in the relevant article and die in the same day as the repealed act.

Examples

Regulation – enter into force:

Article 2

This Regulation shall enter into force on the day of its publication in the Official Journal of the European Union.

Date of document: 20/01/2015
Date of effect: 21/01/2015; Entry into force Date pub. See Art 2

Regulation – enter into force, application, and exception:

Article 8

This Regulation shall enter into force on the twentieth day following that of its publication the Official Journal of the European Union.

It shall apply from 16 June 2015, with the exception of Article 7, which shall apply from the date of entry into force.

Date of effect: 27/01/2015; Entry into force Date pub. +20 See Art 8
Date of effect: 16/06/2015; Application See Art 8
Date of effect: 27/01/2015; Application Partial application See Art 8

Directive addressed to all Member States:

Article 3

This Directive shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union.

This directive is addressed to the Member States.

Date of effect: 09/01/2015; Entry into force Date pub. +20 See Art 3

Decision or directives which are addressed to a member state (to be notified; art. 297 of TFEU, see above):

Article 2

This Decision is addressed to Hungary.

Done at Luxembourg, 22 June 2012.

Date of document: 22/06/2012
Date of effect: 27/06/2012; Takes effect Date notif.
Date of notification: 27/06/2012

<cdm:resource_legal_date_entry-into-force rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2014-01-31</cdm:resource_legal_date_entry-into-force>

12/03/2019: GIL-GM Provisional application of international agreements (P/12032019/4b)
The OP raised a question regarding how to proceed when the date of provisional application is earlier than the date of entry into force in the context of international agreements. The participants agreed that the date of effect should be set according to the date of provisional application so the act would be in force. Further date of effect fields (e.g. related to notification of ratification) could be added later on if necessary.

It is the date present usually in document´s title. Date of document is a core metadata and therefore the one most widely available (each notice must contain one document date).

The date of the document might correspond to (an appropriate annotation has to be created):

- Date of signature (e.g. treaties, international agreements, legislative acts adopted by ordinary legislative procedure or EU general budget (1) ). For those documents, also Date of signature (SG) has to be created (this is not applicable to the legislative acts adopted by ordinary legislative procedure or budget for the time being).

- Date of adoption (e.g. legislative acts adopted by special legislative procedure; non-legislative acts, decisions adopted by the European Parliament).

- Date of vote (resolutions adopted by the European Parliament, resolutions or opinions adopted by ECSC or COR; resolutions or declarations adopted by bodies created by international agreements). For those documents, also Date of vote (VO) has to be created.

- Date of consolidation (consolidated legislation) (2)

- Date of introduction (transmission) of a parliamentary question or date of answer (for answers to parliamentary questions), as indicated in the OJ

- Date of publication (Official Journal of the European Union or European Court Reports, consolidated version of treaties and documents not containing any of the dates mentioned above)

The date has format YYYY-MM-DD.

1 Definitive adoption of (amending) budget – acts signed by the president of EP (e.g. 32015B1766).
2 It refers to the date of applicability of the last amendment included in consolidation

The date might be accompanied by any of the following annotation:

• Date of adoption
• Date of transmission
• Date of notification
• Date of publication
• Date of answer
• Date of vote
• Date of signing
• Entry into force

If any of dates mentioned in Definition (above) is not known, the date of document is equal to the date of publication in the OJ.

It is preferable to specify the nature of the date of document (date of adoption, date of signing, etc.) by using one of the above mentioned annotations.
Particular attention should be paid to the following cases:

• Legislative acts adopted by the ordinary legislative procedure – the date present in the title + annotation Date of signing.
• Definitive adoption of the budget – the date present in the signature + annotation Date of signing.
• Legislative acts adopted under a special legislative procedure; non-legislative acts – the date present in the title + annotation Date of adoption.
• Treaties, international agreements – the date present in the title or text + annotation Date of signing (this is not applicable to the consolidated version of treaties).
• Resolutions of the European Parliament – the date present in the title + annotation Date of vote.

<cdm:work_date_document rdf:datatype="http://www.w3.org/2001/XMLSchema#date">1973-03-03</cdm:work_date_document>

COUNCIL OF THE UNION
Brussels, 30 May 2011 (01.06)
(OR. fr)
10894/11
LIMITE
JUR 272
INST 279

OPINION OF THE LEGAL SERVICE(*)

* This document contains legal advice protected under Article 4(2) of Regulation (EC)
No 1049/2001 of the European Parliament and of the Council of 30 May 2001 regarding
public access to European Parliament, Council and Commission documents, and not released
by the Council of the European Union to the public. The Council reserves all its rights in law
as regards any unauthorised publication.

Subject: Date of adoption of acts under the ordinary legislative procedure
- application of Article 13 of the Regulation on Committee Procedure (1)

1. The purpose of this opinion of the Legal Service is to clarify the determination of the date on
which acts are adopted under the ordinary legislative procedure.

2. This question has arisen in particular for acts which were adopted before the Committee
Procedure Regulation entered into force on 1 March 2011 and were signed by the Presidents
of the European Parliament and of the Council after that date. Insofar as those acts refer to the
old Decision on Committee Procedure (2), which was repealed on 1 March 2011 by the
Regulation on Committee Procedure, the question arises of the applicability of Article 13 of
the Regulation on Committee Procedure.

3. Under Article 294(4) TFEU, when the Council approves the position of the European
Parliament at first reading "the act concerned shall be adopted in the wording which
corresponds to the position of the European Parliament". The date of adoption of the act is
therefore that on which the Council approved the European Parliament's position.

4. At second reading, the act is deemed to be adopted when:
- within three months following the transmission of the first-reading position of the Council
to the European Parliament, the latter approves the Council’s position or has not taken a
decision (3); in that case, the date of adoption of the act should be considered to be that on
which the European Parliament approved the Council's position or the date when the
three-month period expired; or
- within three months following receipt of the European Parliament's amendments, the
Council approves all the European Parliament's amendments by a qualified majority (4 ); in
that case, the date of adoption of the act should be considered to be that on which the
Council approved the European Parliament's amendments.

5. At third reading, the act is adopted when, within a period of – in principle – six weeks
following the approval of a joint text by the Conciliation Committee, the European Parliament
and the Council adopt the act in question in accordance with that text(5). In that case, the date of
adoption of the act should be deemed to be the date when the act was adopted by the second
of the two institutions.

6. The signing of the act by the presidents of the two institutions, provided for in Article 297(1),
is distinct from the adoption of the act and its value consists solely in authentication of the
act (6). Therefore, even if the date of signing is included in the title of the act, as published in the
Official Journal, as the date of the act, it is not the same as the date of the act's adoption.

7. Furthermore, the Legal Service deems incorrect the practice of including the date of signing
of an act in its title, in that it can lead to confusion as to the date of the act's birth in the legal
system of the EU, despite the systematic inclusion in acts adopted by the ordinary legislative
procedure of a footnote specifying the dates on which the European Parliament and the
Council adopted their positions.

8. In conclusion, the Legal Service considers that it follows from Article 294 TFEU that the date
on which an act is adopted by the ordinary legislative procedure is the date of the decision of
the arm of the legislature that acts later (see paragraphs 3 to 5 above) and not the date of the
joint signing of the act by the presidents of the European Parliament and of the Council.
Article 13 of the Regulation on Committee Procedure therefore applies to acts adopted before
1 March 2011 but signed after that date.

(1) Regulation (EU) No 182/2011 of the European Parliament and of the Council of
16 February 2011 laying down the rules and general principles concerning mechanisms for
control by Member States of the Commission’s exercise of implementing powers (OJ L 55,
28.2.2011, p. 13).
(2) Council Decision 1999/468/EC of 28 June 1999 laying down the procedures for the exercise
of implementing powers conferred on the Commission (OJ L 184, 17.7.1999, p. 23).
(3) Article 294(7)(a) TFEU.
(4) Article 294(8)(a) TFEU.
(5) Article 294 (13) TFEU.
(6) However, as the Court of Justice has already held, failure to sign an act is an infringement of
an essential procedural requirement of the act, which may, even automatically, entail the
annulment of the act concerned by the EU's courts (Judgment of 6 April 2000 in cases
(C-287/95 and C-288/95, ECR 2000 p. I-2391, paragraph 55) Commission v. Solvay.

2015/12/22: Decisions of the European Parliament and of the Council on the mobilisation of the European Globalisation Adjustment Fund – e.g. 32015D0738
Methodology related to those documents will be completed. For the time being, Document date should contain the date from the title + comment "Date of adoption".

2017/06/30: Note from the Legal Service of the Council concerning the date of adoption of the acts adopted under the ordinary legislative procedure

Date of dispatch for transmission to one of the institutions.

The date has format YYYY-MM-DD.

The date of dispatch field contains:

For sector 5:
Date of transmission of Commission proposals to the Council
Date of transmission of European Parliament resolutions to parties concerned
Date of transmission of EESC opinions to the Council and the Commission

The source to be used is related procedure (e.g. date of event "Transmission to Council").

For legislative proposals (but also other COM or JOIN documents), if the procedure is not yet available, insert the same date as in the document date field (date of dispatch is usually equal to the date of document). If possible, Annotations should be used ("Forwarded to the Council", "Forwarded to the Parliament", etc.).

In some cases, this information can be found in the text.

For sector 9:
Written questions: date of acknowledgment by the recipient
Oral questions: date of the session
(If such date is not known, insert the same date as in the document date field.)

cdm:resource_legal_date_dispatch rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2000-10-26</cdm:resource_legal_date_dispatch>

31/10/2019: How is this date treated in IMMC?

Date of debate is used to index European Parliament resolutions or of committees (EESC/CoR) opinions.
The date has format YYYY-MM-DD.

The date of debate is indicated in the relevant OJ.

<cdm:act_preparatory_date_debate rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2013-10-16</cdm:act_preparatory_date_debate>

02/05/2015: There are currently two fields duplicating the same information – DB (date of debate) and VO (date of vote). Both were used for different notices in the past. Date of debate is usually not indicated in the OJ, there is only information concerning the session (e.g. 109th plenary session, 3—4 December 2014). Both dates should be present in DB field, but it can currently contain only one date. This should be clarified with the CELLAR.

31/10/2019: Clarification concerning differences and use cases for date of vote and date of debate. How are those dates treated in IMMC?

It is the date on which the act ceases to be valid.

The date has the format YYYY-MM-DD or 9999-12-31 (a fictional date for documents whose validity is indefinite).

The end of validity date is also used as an indicator for the production of the Directory of legislation in force and of the Directory of preparatory acts.

These are the possible cases according to the nature of particular acts:

(a) Acts of limited duration: The date of end of validity mentioned in the act. If the act has a specific expiration date, the end of validity date is followed by the comment See article where the date is specified):

End of validity date: 30/11/2008; See Art. 9

(b) Acts of unlimited duration: Fictional date 9999-12-31

(c) Repealed acts: The current end of validity date of the repealed act has to be changed as follows:

End of validity date of the repealed act = date of effect of the repealing act (or date of its application if it is different as the date of entry into force ) minus 1 day.

The end of validity date is followed by the comment Repealed by and the Celex identifier of the repealing act. The information is completed by creation of the relation repealing act → repealed act:

End of validity date: 26/01/2013; Repealed by 32013R0075

(d) Extention of the validity: If the end of validity of an act has been extended by a subsequent act, the end of the validity date of the amended act has to be changed accordingly. Comment Ext. valid. by and the Celex identifier of the amending act has to be added:

End of validity date: 30/09/2014; Ext. valid. by 32013D0468

(e) Acts only repealing (or extending validity of) an earlier act and not containing any other autonomous provisions die in the same day as the repealed act.

(f) Acts repealed by acts which should be notified, acts declared null and void by a corrigendum and implicitly repealed amending acts (detailed methodology is explained in Exceptions and special cases).

There is no impact to the end of validity date if only a part of the act is repealed by a subsequent act (partial repeal).

(g) Acts that by their nature have no end of validity: Fictional date 9999-12-31.

(h) Legislative proposals (drafts, MS initiatives, drafts of general/amending budgets…):

Fictional date 9999-12-31, to be changed into a factual date when the proposal is adopted (date of adoption of the pursuant legislative act); withdrawn (date of the document stating the withdrawal); rejected (date when the proposal was rejected) or replaced (date of adoption of the amended proposal).

(i) Acts listed as obsolete in documents from sector 5: Date of validity of obsolete acts = sector 5 document publication date.

Example (32002R1429 – listed in 52011XC1108(01))
Date of document: 02/08/2002
Date of effect: 01/07/2002; Implementation See Art 7
Date of effect: 06/08/2002; Entry into force Date pub. +3 See Art 7
End of validity date: 08/11/2011; Obsolete See 52011XC1108(01) P 1

(j) Acts related to the budget and to the specific financial year: Such acts have only limited duration (until the end of the relevant financial year).

Example 32011B0840
Date of document: 28/10/2011
Date of effect: 01/01/2011; Entry into force Financial year 2011
End of validity date: 31/12/2011; Financial year 2011

(k) Acts related to the common agricultural policy or fisheries and to the specific marketing year: Such acts have only limited duration (until the end of the relevant marketing year; Definition of the marketing year could be find in article 6 of 32013R1308).
The same rule and comment should be applied for all acts referring to the specific fishing season (31972R2825).

Example 32009R0274 (Commission Regulation (EC) No 274/2009 of 2 April 2009 fixing the quantitative limit for the exports of out-of-quota sugar and isoglucose until the end of the 2009/2010 marketing year)
Date of document: 02/04/2009
Date of effect: 10/04/2009; Entry into force Date pub. + 7 See Art 3
Date of effect: 01/10/2009; Implementation See Art 3
End of validity date: 30/09/2010; End of season 2009/2010 (comment + year)

32016R2361 (Commission Regulation (EU) 2016/2361 of 15 December 2016 establishing a prohibition of fishing for Greater forkbeard in Union and international waters of VIII and IX and Union and international waters of V, VI, VII by vessels flying the flag of Portugal)

Article 1
Quota exhaustion
The fishing quota allocated to the Member State referred to in the Annex to this Regulation for the stock referred to therein for 2016 shall be deemed to be exhausted from the date set out in that Annex.

Date of document: 15/12/2016; Date of adoption
Date of effect: 23/12/2016; Entry into force Date pub. +1 See Art 3
End of validity date: 31/12/2016; Period of reference 2016 (comment + year)

If it is not possible to determinate the exact dates of the marketing/fishing year and if the application of the act is not directly related to the marketing/fishing year, the end of validity should be a fictional date 9999-12-31.

(l) Ephemeral acts (acts related to day-to-day management of agricultural measures whose titles are printed in light type in OJ cover page): Such acts are generally valid only for a limited period and are automatically repealed by subsequent acts.
For such acts, EV field should not be created.

There is no in force indicator for ephemeral acts.

(m) Regulations opening an invitation to tender for specific agricultural products: End of validity date is usually mentioned in the provisions (The invitation should be open until DD/MM/YYYY).

(n) Acts concerning the appointments of members for a defined period: End of validity date is equal to the last day of the period mentioned in the provisions.

Example 32014D0047
Date of document: 28/01/2014
Date of effect: 28/01/2014; Entry into force Date of document See Art 2
End of validity date: 25/01/2015; End of term of office See Art. 1

(o) Anti-dumping measures (explained below in Exceptions and special cases)

(p) Documents from sector 5: End of validity date is mainly applicable to proposals, drafts, MS initiatives (see point (d) above) or ECB recommendations.

For different documents from the decision-making process other than proposals, the EV date is applicable only for exceptional cases (e.g. EP legislative resolution repealing/replacing the previous one; no examples in the database).

<cdm:resource_legal_date_end-of-validity rdf:datatype="http://www.w3.org/2001/XMLSchema#date">9999-12-31</cdm:resource_legal_date_end-of-validity>

Acts repealed by a subsequent act – End of validity date of repealed acts

• Acts repealed by acts which should be notified
An act is repealed by another act whose legal value depends of the date of notification.
If the notification date is not yet known, the end of validity date of the repealed act should have the following value, accompanied by the comment “repealed by” and the mention of the repealing act:

Date of document: 12/12/2013
Date of effect: 08/01/2014; Entry into force Date pub. +20 See Art 2
End of validity date: 31/12/9999 ; Repealed by 32011D0395

That date is to be modified once the notification date of the amending act is known and implemented in its notice.

• Acts declared null and void by a corrigendum
In such cases, the end of validity date is equal to the date of publication of the first act (and not to the date of the corrigendum).

Such formation must be completed by the creation of an active relation corrigendum → corrected act (for the comment to be added, see Relations).

Example 32013R1363, published in OJ L 343 of 19.12.2013 (before the corrigendum was published):
Date of document: 12/12/2013
Date of effect: 08/01/2014; Entry into force Date pub. +20 See Art 2
End of validity date: 31/12/9999

Document 32013R1363R(01) (corrigendum published in OJ L 343 of 20 December 2013) declares the publication of Commission Delegated Regulation (EU) No 1363/2013 to be considered null and void.

Document 32013R1363 (after the corrigendum 32013R1363R(01) was published):
Date of document: 12/12/2013
Date of effect: 08/01/2014; Entry into force Date pub. +20 See Art 2
End of validity date: 19/12/2013 See 32013R1363R(01)

Implicitly repealed amending acts

Basic act: Any act from sector 2, 3, 4 or 5 which has subsequently been modified.

Amending act: Any act which fully or partially modifies the basic act to which it relates. An amending act can be composed either of provisions which only relate to one basic act ("not-autonomous provisions") or of provisions which relate to more than one or to none basic act, and which produce a legal effect of their own (“autonomous provisions”).

An amending act is deemed implicitly repealed when the basic act to which it relates is repealed and does not explicitly mention that its successive amendments are also repealed, as long as the amending does not contain any autonomous provisions.

The end of validity date of the amending act should be the same as the one of the repealed basic act.

The information must be completed by the creation of an active relation act repealing the basic act → amending act (for implicitly repeals, see Relations).

See also comment (21/9/2015) Implicitly repealed amending acts – information form the Legal Service

Anti-dumping measures

A definitive anti-dumping measure shall expire five years from its imposition or five years from the date of conclusion of the most recent review (Council regulation (EC) No 1225/2009, art. 11.2).

There are two basic scenarios for the amendments concerning the end of validity date of an implementing measure:

Scenario 1

Publication of: Basic implementing regulation imposing a definitive anti-dumping duty
Date of application = 01-01-2014
End of validity date = 31-12-2018

Publication of: Implementing regulation amending the basic regulation (not repealing or amending the validity)
Date of application = DD-MM-YYYY
End of validity date = 31-12-2018

Publication of: Notice of the impending expiry of certain anti-dumping measures
(Published in OJ before the expiry of the basic regulation.)
No change needed for the end of validity of the basic implementing regulation or the amending regulation.

Scenario 2 (the dates in EV date are to be used successively, following the sequence of events described below)

Publication of: Basic implementing regulation imposing a definitive anti-dumping duty
Date of application = 01-01-2014
End of validity date = 31-12-2018

Publication of: Implementing regulation amending the basic regulation (repealing or amending the validity, in this case to 31-12-2019)
Date of application = DD-MM-YYYY
End of validity date = 31-12-2019 + change of the end of validity date of the basic implementing regulation to be done

Publication of: Notice of initiation of partial interim review of the anti-dumping measures
The basic implementing regulation should remain in force pending of the outcome of the review:
The end of validity date of the basic and amending implementing regulations has to be changed, until the review is published (should be changed to 31-12-9999)

Publication of: New basic implementing regulation imposing a definitive anti-dumping duty
Date of application = 01-04-2020
End of validity date = 31-03-2025
The end of validity date of the basic (A) and amending implementing (B) regulations has to be changed to the definitive date (31-03-2020 – date of application of the new basic regulation minus one day).

2015/09/21: Implicitly repealed amending acts – information form the Legal Service
When a legal act is repealed, it is repealed with all subsequent amendments, even when they are not listed in the repealing act, unless for specific reasons it is expressly provided that certain amending acts are not repealed together with the main act.

2015/09/23: Recommendations from sector 3
Generally, recommendations from sector 3 should not have the end of validity.
It should be created only if there is another document repealing some of the previous recommendations (e.g. 32014H0897). NB: Currently there are 1058 recommendations in sector 3 containing EV date (DTS_SUBDOM = LEGISLATION AND FM = "RECOMM" NOT EV=NULL). Correction to be done.

15/12/2016: End of validity of repealed acts
Manual of precedents for acts established within the Council of the EU, 2002:

3. REPEAL

The repeal of an act or of certain of its provisions means that it/they cease( s) to be in force, either because the arrangements that it/they introduced expire or are replaced by other arrangements, or because the whole act, including all its successive amendments is replaced by a codified/recasted act (*).

Regulation ...... [and Regulation ...... taken in implementation thereof] shall be repealed. 1

Article 3 of Regulation ...... shall be repealed.

NB: In these two cases it is understood that the repeal takes effect on the date of entry into force or, where appropriate, the date of application of the repealing act.

Regulation ...... shall be repealed with effect from ...... [date on which the repealing

Regulation is brought into effect].

NB: In that case, the repeal shall take effect on a date which differs from that of the entry into force of the repealing act.

(*) "Consolidating act" from the original version was replaced by "a codified/recasted act.

28/02/2017: Ephemeral acts, fisheries - prohibition of fishing
Change of the methodology for ephemeral acts – EV not to be created.
Documents related to prohibition of fishing – there should be a real EV date inserted, based on the text.

29/06/2017: Information from SJ concerning validity of delegated/implementing acts
A delegated/implementing/comitology act does not automatically get repealed on the repeal of the basic legislative act on the basis of which it got adopted. An act is valid if its legal basis was valid at the time of adoption of the act. Such a delegated/implementing/comitology act would need to be specifically repealed by the Commission

15/03/2019: Association agreements – new Member States
Notices covering the associationagreements with new MS contain value 31/12/9999 in EV date. Therefore, the in force indicator says "In force".
We assume the EV date should be equal to the date of accession (minus 1 day); but this assumption has not been confirmed by any relevant authority.
Based on this, it was decided to remove EV field from such notices.
See https://webgate.ec.europa.eu/publications/jira/browse/LAAION-540
Examples: 22005A0617(02), 22005A0617(01), 22003A0515(01), 21993A1231(18), 21993A1231(15)
29/09/2016: GIL-GM Amended proposal – end of validity date of the initial proposal
Commission proposal can be amended a couple of times and that such amended proposals are published as separate notices on EUR-Lex. The questions is whether the end of validity date of the initial proposal can be understood as being the date of the adoption of the 1st amended proposal (minus 1 day) and whether the end of validity date of the 1st amended proposal can be understood as being the date of the adoption of the second amended proposal (minus 1 day)? Or should the first and second amended proposals be understood only as texts amending the initial proposal but not replacing it? The amended proposals can contain only the amendments or the amendments plus the original proposal, depending on the case-by-case basis.
The participants agreed that both the initial proposal and the amended proposal(s) should keep having the fictional date of end of validity (implying that they are "pending"), until a final act is adopted. After this, the date of adoption of the final act becomes the date of end of validity of both the initial proposal and amended proposals.

12/03/2019: GIL-GM Follow-up of Court's decisions on annulment (P/12032019/4a)
The legal analysis methodology does not follow up on the annulments of legal acts by judgments of the Court of Justice. Currently the date of end of validity of those acts remains indefinite; therefore, they remain marked as 'in force'.
The Commission Legal Service was consulted and considered that the effect should be as if it had never existed, therefore the value contained in the date of effect field should be reproduced in the date of end of validity, and the in force indicator switched to 'not in force'. The participants agreed on this solution and indicated that the comment 'declared void by' should be shown below the title, next to the in force indicator coloured point.
This solution should also be applied to cases where the judgment annuls the decision but orders to maintain the effects of the decision in force.

Example https://eur-lex.europa.eu/legal-content/EN/ALL/?qid=1571896291605&uri=CELEX:62011CJ0658:

On those grounds, the Court (Grand Chamber) hereby

1. Annuls Council Decision 2011/640/CFSP of 12 July 2011 on the signing and conclusion of the Agreement between the European Union and the Republic of Mauritius on the conditions of transfer of suspected pirates and associated seized property from the European Union-led naval force to the Republic of Mauritius and on the conditions of suspected pirates after transfer;

2. Orders that the effects of Decision 2011/640 be maintained in force

12/03/2019: GIL-GM End of validity of international agreements when the decision on the signing was declared void by CdJ (P/12032019/4b)
The OP raised the question on how to proceed when the Court annuls the decision on the signing of an agreement. The participants agreed that in both decision and agreement cases the value corresponding to the date of entry into force should be set in the date of end of validity field.
See for example https://eur-lex.europa.eu/legal-content/EN/ALL/?qid=1571896291605&uri=CELEX:22011A0930(01)

Date of deadline field contains various intermediate deadlines relating to the document.

The date has format YYYY-MM-DD.

Deadline/expiry date is mentioned in the act (it is a date other than the implementation date or than the date of end of validity). Several dates per document can be entered.

The field is used for legislation and is optional.

Special attention has to be paid to review clauses in legislation.

Often, such clauses are in the form of an article entitled "Review", rather at the end of the text of the legal act (or international agreement).

Example (32013L0050):

Article 5
Review

By 27 November 2015, the Commission shall report on the operation of this Directive to the European Parliament and the Council, including on its impact on small and medium-sized issuers and on the application of sanctions, in particular whether they are effective, proportionate and dissuasive, and shall review the functioning and assess the effectiveness of the retained method for the purposes of calculating the number of voting rights relating to the financial instruments referred to in the first subparagraph of Article 13(1a) of Directive 2004/109/EC.

The report shall be submitted together with a legislative proposal, if appropriate.

For such case, an annotation to the deadline must be created, containing value B-19.12 (Review) from FD_305. It should be used for the field "Deadline (DL)" like this:

<annot:comment_on_date>{B-19.12|http://publications.europa.eu/resource/authority/fd_335/B-19.12}</annot:comment_on_date>

<cdm:resource_legal_date_deadline rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2014-12-31</cdm:resource_legal_date_deadline>

Date of signature field provides the date or dates of the signing of an legislative act, agreement or EU budget. This field may also contain a reference to the place where the agreement was signed.

The date has format YYYY-MM-DD.

Date of signature as indicated in the text. The field might contain multiple data (in case of different dates and places of signature).

Date of signature (e.g. treaties, international agreements).

Not applicable to the legislative acts adopted by ordinary legislative procedure or budget (for the time being - 2018).

<cdm:resource_legal_date_signature rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2014-03-25</cdm:resource_legal_date_signature>

31/10/2019: Check if this date shall be also available in legislative acts & budget

This field contains the date of notification of directives and decisions which specify to whom they are addressed.

The date has format YYYY-MM-DD.

According to article 297 of TFEU, other directives, and decisions which specify to whom they are addressed, shall be notified to those to whom they are addressed and shall take effect upon such notification.

For above mentioned directives and decisions, the deadline for transposition usually begins to run from the date of notification.

The following cases are possible:

(1) The date of effect is not indicated in the act, it is linked to the date of notification (see 32015D1410):

This decision shall take effect on the date of its notification.

The date of notification is usually provided to the OP after the publication of the relevant act in the OJ.

For such cases 01-01-1001 should be inserted to the NF field.

Please note that the Date of effect field (IF) should contain a comment Takes effect (for directives/decisions which specify to whom they are addressed).

The date of notification (as well as the date of effect) will be changed to a real date after receiving it from the relevant service.

(2) The Date of effect (IF) is indicated in the act and it is not linked to the Date of notification (NF) (see 32015D1023):

This decision shall enter into force on the date following that of its publication in the Official Journal of the European Union.

Some Council acts (decisions or directives which specify to whom they are addressed; but also Decisions of representatives of the governments of the Member States or recommendations) may contain a date of notification not linked to the date of effect (which is indicated in the act). In this case the date of notification will be created after receiving it from the relevant service. The Date of effect field will not be impacted by this change.

<cdm:legislation_secondary_date_notification rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2014-01-31</cdm:legislation_secondary_date_notification>

14/10/2015: Methodology
related to the Council decisions or directives which specify to whom they are addressed and indicating the date of effect was updated (Analytical methodology, point 2).

2017/10/16: EFTA Surveillance Authority Decision having addressees: Date of document (=date of adoption) = the date of notification (and therefore date of effect)

From: Mathisen, Gjermund [mailto:Gjermund.Mathisen@eftasurv.int]
Sent: jeudi 12 octobre 2017 11:16
To: BRKIC Dejan (OP)
Cc: Jordal, Christian; OP LEGAL ANALYSIS
Subject: RE: EFTA decisions - date of notification

Dear Mr Brkic,

We will attempt to add that to our routines, yes. (I note, to be more precise, that I would not expect this to happen every year; it’s more exceptional than that.)

Kind regards,

Gjermund Mathisen
Director of Competition and State Aid

Rue Belliard 35, 1040 Brussels

Phone: +32 2 286 18 60 (direct line)
Phone: +32 2 286 18 21 (assistant)
E-mail: Gjermund.Mathisen@eftasurv.int
www.eftasurv.int

From: BRKIC Dejan (OP) [mailto:Dejan.BRKIC@publications.europa.eu]
Sent: 12 October 2017 11:04 AM
To: Mathisen, Gjermund <Gjermund.Mathisen@eftasurv.int>
Cc: Jordal, Christian <Christian.Jordal@eftasurv.int>; OP LEGAL ANALYSIS <OP-LEGAL-ANALYSIS@publications.europa.eu>
Subject: RE: EFTA decisions - date of notification

Dear Ms Mathisen,

Thanks a lot for this confirmation.
It would be good if you could also inform us about those exceptional cases where the date of adoption is not the date of notification. You can do so by sending an e-mail to our functional mailbox
OP-LEGAL-ANALYSIS@publications.europa.eu

Kind regards,

Dejan BRKIC
Legal Analysis and Documentary Management
_________________
Publications Office of the European Union
Dissemination and Reuse Directorate
Documentary Management and Metadata Unit

2985 Luxembourg • LUXEMBOURG
Tel: +352 2929 42217
Dejan.BRKIC@publications.europa.eu
http://publications.europa.eu


From: Mathisen, Gjermund [mailto:Gjermund.Mathisen@eftasurv.int]
Sent: jeudi 12 octobre 2017 10:10
To: BRKIC Dejan (OP)
Cc: Jordal, Christian
Subject: RE: EFTA decisions - date of notification

Dear Mr Brkic,

I have had your email below forwarded from the EFTA Secretariat. My apologies for getting back to you so late.

Indeed, you may assume that any decisions in the field of State Aid or Competition, which are addressed to a specific addressee, be that a State or (a) private party/ies, apply as from the date of adoption. As a rule, we always notify such decisions to the addressee(s) on the date of adoption. If, exceptionally, we should fail to do so, we will notify the EFTA Secretariat of the notification date.

I hope this answers your question.

Kind regards,

Gjermund Mathisen
Director of Competition and State Aid

20/02/2019: If the real date of notification is not known, the date of publication + annotation The act was notified but the date of notification is not available on EUR-Lex – the date of publication is used instead
<COMMENT_ON_DATE>{titleAndReference.draft.disclaimer.new|http://publications.europa.eu/resource/authority/fd_365/titleAndReference.draft.disclaimer.new}</COMMENT_ON_DATE>
Additionally, if the date of effect depends on the date of notification, the date of publication shall be also used in IF field.
Example: https://eur-lex.europa.eu/legal-content/EN/ALL/?qid=1550651686388&uri=CELEX:32015D0248

Date of the answer of the institution to a parliamentary question.

The date has format YYYY-MM-DD.

The date of reply field contains:
• for written questions, the date of receipt of a reply to the European Parliament;
• for other questions, the date of the debate or written reply.

<cdm:question_parliamentary_date_reply rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2013-02-18</cdm:question_parliamentary_date_reply>

Date on which directives (or other acts) have to be implemented by the Member States (transposed into its national law).

Transposition date as indicated in the text.

This field might contain multiple dates – different deadlines can be provided for different aspects of the directive.

The usual way how the date of transposition is indicated is the following:
Date of transposition: 30/09/2014; At the latest See Art 2

<cdm:directive_date_transposition rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2014-09-30</cdm:directive_date_transposition>

31/10/2019: List of relevant subproperties:
cdm:directive_date_transposition
cdm:decision_date_transposition
cdm:recommendation_date_transposition
cdm:recommendation_ecsc_date_transposition
cdm:regulation_date_transposition
cdm:cooperation_police-and-judicial_date_transposition

31/10/2019: To be checked which properties are used + remove those that are not needed

Tools used for classification of the documents (Directory code, Subject matter) or for describing of the content (EuroVoc).

Directory is a numerical classification tool. It offers access to EU law by subject.

What are the Directory Codes?

The Directory is a classification that consists of 20 chapters with subdivisions covering the main activities and competences of the EU.
Strictly speaking, the directory codes are the numbers given to every chapter and subdivision in the Directory, each of them covering a specific area of European Union activity. For example:

03.20 Agricultural structural funds

The Directory Code has a tree structure and it can be browsed online or it can be loaded in PDF format from the EUR-Lex website or in XML or SKOS format from the MDR svn (table FD_555).

The EUR-Lex Directory gives access to European Union legal acts / acts of EU legislation, but also to other instruments such as preparatory and informative documents, agreements and conventions concluded by the EU and to other non-binding instruments relating to policy activities such as declarations, guidelines, reports, etc

The structure and the subdivisions of the Directory mat change with the time. It is foreseen to perform modifications in the Directory in order to make it conform with the Treaties in force and to cover all the competencies and policies of the EU.

Currently, the following directories are available on the EUR-Lex:

Directory of European Union legislation
Directory of European Union preparatory acts
Directory of European Union consolidated acts
Directory of international agreements

There is a specific directory classification for EU case law (Directory of European Union case law before Lisbon and after Lisbon).

The aim is to provide a selection from the EUR-Lex database reflecting the current state of EU law.

Each descriptor is composed of eight digits corresponding to the principal chapter heading and up to three subsequent subdivisions, each represented by two digits.

Documents may be indexed with up to three directory codes.

It is also used for special editions of the Official Journal of the European Union for indicating the number of chapter (see Official Journal special edition chapter)

The chapter headings are following:

01 General, financial and institutional matters
02 Customs Union and free movement of goods
03 Agriculture
04 Fisheries
05 Freedom of movement for workers and social policy
06 Right of establishment and freedom to provide services
07 Transport policy
08 Competition policy
09 Taxation
10 Economic and monetary policy and free movement of capital
11 External relations
12 Energy
13 Industrial policy and internal market
14 Regional policy and coordination of structural instruments
15 Environment, consumers and health protection
16 Science, information, education and culture
17 Law relating to undertakings
18 Common Foreign and Security Policy
19 Area of freedom, security and justice
20 People's Europe

Documents should never be indexed by "root level" directory codes (ex: 20.00.00.00) but rather at a more specific level.

Documents may be indexed with up to three directory codes.

Users should be able to find, under each directory heading, all of the documents dealing specifically with the given subject without having to browse through subheadings or other headings. When the document deals with one special issue, indexing must then be done using the most specific descriptor fitting as properly as possible the topic covered by the document. If no existing heading specifically suits the document, it has to be filed under the closest more general entry.

As a consequence, the same document should never be indexed simultaneously using, within the same directory, a general heading and a more specific heading positioned hierarchically underneath it.

For example, the same document should bear one proper descriptor and not be labelled as such:
07.20.30.00 Transport policy / Inland transport / Market operation
07.20.30.30 Transport policy / Inland transport / Market operation / Transport prices and terms

When a document deals with multiple topics related to several sub-headings of the same chapter, instead of indexing under one general entry, multiple headings should be chosen provided they all are of the same level. However, it is better to minimize the number of descriptors used to prevent that acts are published in several places in the directory.

For example, a text regarding both excise duties and individual tax exemptions should be analysed as such:
09.30.20. Taxation / Indirect taxation / Excise duties
09.30.40. Taxation / Indirect taxation / Individual tax exemptions

and not 09.30. Taxation / Indirect taxation

The classification of EUR-Lex documents with the Directory Codes will have to be performed in line with the ISO 5963 standard, completed with what the guidelines as stated in this document.

Basic rules

What is document classification?

Classification consists of assigning documents to one or more categories based on their main topics. When classifying, it must be kept in mind that it is not the content of the document that is being described (indexation) but the main subject(s) that the document covers (classification).

Basic principles of classification:

• Follow the three stages of classification:

o Examination of the document (intellectual analysis).
o Identification of the main topic(s) covered by the document.
o Selection of the directory codes that correspond with the main topics previously identified.

• Be as specific as possible. Choose the directory code(s) which adjust better to the main topic(s).

• Do not classify a document with two directory codes (general and specific) belonging to the same hierarchical line. It is possible to use various codes under the same domain but it is not possible to use the main domain and one of its subdivisions. For example:

Correct: 03.20.30.00 Agriculture / Agricultural structural funds / European Agricultural Fund for Rural Development
Incorrect: 03.00.00.00 Agriculture

• Keep the end-user in mind. The directory codes are employed by the user for document retrieval therefore it is important to select the directory codes which have a potential value for the users. If a document is not correctly classified the user will get irrelevant results in its query.

• Be careful with the "General" or "Miscellaneous" categories. These must be used only if no other subdivision is adequate for the classification of the document. An overuse of these categories leads to "noise" after a query (retrieval of numerous documents which are not relevant to the user).

Classification guidelines – How to assign directory codes:

The first directory code to be assigned will conform to the following instructions:

EU legislation must be based on an appropriate treaty provision which means that each institution must act within powers conferred by a treaty.
The legal basis of EU legal acts are mentioned in the documents. The make reference to the provision which confers competence to adopt the act in question.
Treaty provisions are grouped under Treaty titles, chapters, sections or in protocols. Since the Directory codes cover the EU activities and competences, a correspondence can be set up between the Treaty titles, chapters, etc and the subdivision of the Directory.
It means that the legal basis can be used as solid information to classify the legal acts and for this a correspondence table between the articles of TEU and TFEU and the Directory Codes has been created.

If in the correspondence table there is a reference to one of the main domains in the Directory Codes (e.g. 01 General, financial and institutional matters) it means that, if possible, the classifier will have to choose the most specific subdivision within the main domain.
If in the correspondence table there is a reference to more than one directory code the classifier must choose the most specific subdivision form each chapter or from the most adequate chapter of the Directory.

The subsequent directory codes (if any) will be assigned following the basic classification principles previously mentioned.
The legal basis of non-legislative acts makes reference to a basic act. In this case, the Treaty provision of this act has to be used for classification.
Preparatory documents don't have a legal basis, but usually there is mention to the legal basis of the proposed act which can be used for classification.

The minimum number of directory codes that can be assigned to a document is one (1). There is no maximum number of directory codes that can be assigned to a document, but it is recommended not to use more than three (3).

<cdm:resource_legal_is_about_concept_directory-code rdf:resource="http://publications.europa.eu/resource/authority/fd_555/1530"/>

In order to maintain consistency, some rules must be respected by the indexation:

For modifying documents, the same descriptors should be used as for the modified document.

For documents related to the anti-dumping – 11.60.40.20 Anti-dumping measures should be always used.

For legislation adopted on a legislative proposal, use the descriptors from the proposal.

For agreements adopted by decision of the Council, use the same descriptors as in the act adopting the agreement.

For documents concerning the budget use 01.60.20 Budget.

Correspondance between TEU & TFEU and directory concepts

Treaty on European Union

Articles 1-8: 01.10 Principles, objectives and tasks of the Treaties
Articles 9-12: 01.10 Principles, objectives and tasks of the Treaties / 20.20 European citizenship
Articles 13-19: 01.40.00.00 General, financial and institutional matters / Provisions governing the institutions
Article 20: No specific heading for administrative cooperation. GO TO: the different domains where the cooperation takes place i.e. taxation, judicial cooperation, patents, civil law, etc.
Articles 21-22: 11 External relations
Articles 23-46: 18 Common Foreign and Security Policy
Articles 47-55: 01.10 Principles, objectives and tasks of the Treaties / 01.30 Scope of the Treaties

Treaty on the functioning of the European Union

Articles 1-6: 01.10 Principles, objectives and tasks of the Treaties
Articles 7-17: 01.10 Principles, objectives and tasks of the Treaties
Articles 18-25: 20.20 European citizenship
Articles 26-27: 13.30 Internal market: approximation of laws / 13.40 Internal market: policy relating to undertakings
Articles 28-32: 02 Customs Union and free movement of goods
Article 33: 19.30.30 Customs cooperation
Articles 34-37: 08.90.00.00 Competition policy / National trading monopolies
Articles 38-44: 03 Agriculture / 04 Fisheries
Articles 45-48: 05.10 Freedom of movement for workers
Articles 49-62: 06 Right of establishment and freedom to provide services
Articles 63-66: 10.40 Free movement of capital
Articles 67-76: 19 Area of freedom, security and justice
Articles 77-80: 19.10.10 Elimination of internal border controls / 19.10.20 Crossing external borders / 19.10.30 Asylum policy / 19.10.40 Immigration and the right of nationals of third countries
Article 81: 19.20 Judicial cooperation in civil matters
Articles 82-86: 19.30.20 Judicial cooperation in criminal matters
Articles 87-89: 19.30.10 Police cooperation
Articles 90-100: 07 Transport policy
Articles 101-106: 08 Competition policy
Articles 107-109: 08.60 State aids and other subsidies
Articles 110-113: 08 Competition policy
Articles 114-118: 08 Competition policy / 17.20 Intellectual property law
Article 119: 10.20 Monetary policy / 10.30 Economic policy
Articles 120-126: 10.30 Economic policy
Articles 127-133: 10.20 Monetary policy
Articles 134-135: 10.20.10 Institutional monetary provisions / 10.30.10 Institutional economic provisions
Articles 136-138: 10.30.30 Economic and monetary union
Articles 139-144: 10.30.30 Economic and monetary union
Articles 145-150: 05.20.30 Employment and unemployment
Articles 151-161: 05.20 Social policy
Articles 162-164: 05.20.10 European Social Fund (ESF)
Articles 165-166: 15.30 Health protection / 16.30 Education and training (No specific domain for Sport in the Directory Codes)
Article 167: 16.40 Culture
Article 168: 03 Agriculture (03.50.20 Plant health; 03.50.30 Animal health and zootechnics) / 15.30 Health protection
Article 169: 15.20 Consumers
Articles 170-172: 13.60 Trans-European networks
Article 173: 13.10 Industrial policy: general, programmes, statistics and research / 13.20 Industrial policy: sectoral operations
Articles 174-178: 14 Regional policy and coordination of structural instruments
Articles 179-190: 13.10.30 Research and technological development / 16.10 Science (No specific domain for Space in the Directory Codes)
Articles 191-193: 15.10 Environment
Article 194: 12 Energy
Article 195: 06.20.20.50 Right of establishment and freedom to provide services / Sectoral application / Service activities / Leisure services // 13.20.70.00 Industrial policy and internal market / Industrial policy: sectoral operations / Other industrial sectors (No specific domain for Tourism in the Directory Codes)
Article 196: 15.20.30.00 Environment, consumers and health protection / Consumers / Protection of health and safety
Article 197: No specific heading for administrative cooperation. GO TO: the different domains where the cooperation takes place i.e. taxation, internal market, external relations, etc.
Articles 198-204: 11.70.40.10 External relations / Development policy / Associations / Overseas countries and territories (PTOM)
Article 205: 11.50 External relations / Action in favour of countries in transition // 11.70.20.00 External relations / Development policy / Aid to developing countries
Articles 206-207: 11.60.10.00 External relations / Commercial policy
Articles 208-214: 11 External relations
Article 215: 18 Common Foreign and Security Policy
Articles 216-219: 11 External relations
Articles 220-221: 11.30.40.00 External relations / Multilateral relations / Cooperation with international and non-governmental organisations
Article 222: 14.40.20.00 Regional policy and coordination of structural instruments / Autonomous regional action / Aid for stricken regions
Articles 223-234: 01.40.20 Parliament
Articles 235-236: 01.40.00.00 General, financial and institutional matters / Provisions governing the institutions (No specific heading in the Directory Codes)
Articles 237-243: 01.40.30 Council
Articles 244-250: 01.40.40 Commission
Articles 251-281: 01.40.50 Court of Justice
Articles 282-284: 01.40.75 European Central Bank
Articles 285-287: 01.40.60 Court of Auditors
Articles 288-299: 01.40.10.00 General, financial and institutional matters / Provisions governing the institutions / General
Article 300: 01.40.65 Committee of the Regions / 01.40.70 Economic and Social Committee
Articles 301-304: 01.40.70 Economic and Social Committee
Articles 305-307: 01.40.65 Committee of the Regions
Articles 308-309: 01.40.80 European Investment Bank
Article 310: 01.60.00.00 General, financial and institutional matters / Financial and budgetary provisions
Article 311: 01.60.30 Own resources
Articles 312-319: 01.60.20.00 General, financial and institutional matters / Financial and budgetary provisions / Budget
Articles 320-324: 01.60.00.00 General, financial and institutional matters / Financial and budgetary provisions
Article 325: 01.60.00.00 General, financial and institutional matters / Financial and budgetary provisions / 09.50.00.00 Taxation / Prevention of tax evasion and avoidance
Articles 326-334: No specific heading for administrative cooperation. GO TO: the different domains where the cooperation takes place i.e. taxation, judicial cooperation, patents, civil law, etc.
Articles 335-358: 01.10 Principles, objectives and tasks of the Treaties / 01.20 General provisions / 01.30 Scope of the Treaties / 01.40 Provisions governing the institutions

EuroVoc is a multilingual and multi-disciplinary thesaurus which covers the field of activity of the European Union. It was originally built up specifically for processing the documentary information of the EU institutions, but is largely used outside the EU institutions as well.

The aim of EuroVoc is to provide the information management and dissemination services with a coherent indexing tool for the effective management of their documentary resources and to enable users to carry out documentary searches using controlled vocabulary.

It is used as an indexing tool for the EUR-Lex documentary collection and as a search tool in the EUR-Lex website.
https://eur-lex.europa.eu/browse/eurovoc.html
https://op.europa.eu/en/web/eu-vocabularies

Part I: General indexing principles – How to use a thesaurus as an indexing tool?

In order to meet the retrieval needs of the end-users of a documentary collection by using thesaurus indexing terms, a number of general indexing principles have to be respected.

The basic principles of subject indexing are the followings:

(1) Index the content of the document

(2) Follow the three stages of indexing:

• examination of the document
• identification of its main subject content
• selection of indexing terms that describe that content

(3) Be as specific as possible

(4) Do not index simultaneously with two descriptors (specific and general) belonging to the same hierarchical line

(5) Prefer pre-coordinated descriptors to simple descriptors

(6) The indexer’s job is only to index, not to interpret, evaluate or diagnose

(7) Use geographical descriptors if possible

(8) Subject indexing should not concern the physical entity of the document

(9) Achieve indexing consistency

These basic indexing rules are also described by the international standard ISO 5963 document entitled Methods for examining documents, determining their subjects and selecting indexing terms.

1. Index the content of the document: use thesaurus terms for document content indexation and not for classification

The thesaurus is an indexing tool. Indexing consists of representing the content of the document with selected descriptors of a thesaurus in the purpose of document retrieval.

Indexation does not consist of classifying documents according to their main subject(s) with a classification scheme or a subject heading list.

Indexation with thesaurus terms is often contrasted to classification with a classification scheme. Classification consists of assigning documents to one ore more categories based on their main topics.

2. Follow the three stages of indexing

Indexation is a complex, intellectual decision process including the following steps:

• 1.2.1 examining the document (intellectual analysis)

In order to be able to analyse the content of documents, indexer should have adequate knowledge of the field covered by the document. Indexer should understand the concepts and main ideas encountered in the document.

• 1.2.2 identifying the principal concepts and the essential elements of the document

In order to be able to select the concepts which have a potential value for the users, indexer should know the purpose for which the indexing terms will be used (document retrieval).

• 1.2.3 expressing the selected concepts in thesaurus terms

In order to be able to represent the selected concepts with thesaurus terms, indexer should have adequate knowledge of the vocabulary he/she is using (structure, preferred terms and non-preferred terms, cross-relations, etc).
Since the meaning of a descriptor is clarified by the thesaurus itself (by the relations of a term with other descriptors), indexer is asked to always examine the contextual and semantic environment of the descriptors:

• Domain
• Microtheasurus
• USE/UF – preferred terms and non-preferred terms
• Top term and narrow terms
• Related terms
• Notes

3. Be as specific as possible

When indexing, the most specific term available in the thesaurus should be selected to represent the given concept. It means that:

• the descriptor chosen to represent the selected concept of the document should be at the same level of specificity as the selected concept

• if the thesaurus has no descriptor at the same level of specificity as the selected concept, the descriptor at the next higher level should be chosen (descriptor which is closest to the concept)

Loss of specificity occurs when a particular concept of a document is represented by an indexing term with more general meaning while an indexing term at the same level of specificity is available in the thesaurus.

Exceptions

In some special cases, indexing at a more general level than the selected concept may be justified. For example:

• when very specific concepts occur only casually or in the fringe area of the document, but the main part of the document is at general level
• when a (long) document covers a lot of specific area (all the specific EU policies or all countries, etc.) which can be summarized in one or more generic terms

4. Do not index simultaneously with several descriptors (specific and general) belonging to the same hierarchical line

The reasons for not indexing simultaneously with two or more descriptors belonging to the same hierarchy are the followings:

• it avoids multiple, redundant indexing
• broader indexing terms are linked to the more specific ones by the hierarchical tree structure of the thesaurus – ascending and/or descending (auto)posting is possible
(In EUR-Lex, if the user searches for a generic term, all the documents indexed with one of its narrower terms will be found)

N.B.: Descriptors on the same hierarchical level and related terms can be used simultaneously.

5. Prefer pre-coordinated descriptors to ‘simple’ descriptors or to the combination of two or more simple descriptors

Pre-coordinated descriptors have been created in order to be able to represent with only one descriptor a complex, compound concept, instead of being obliged to combine several simple descriptors. The use of pre-coordinated descriptors gives better results in document retrieval than the combination of descriptors.

If there is no pre-coordinated descriptor in a thesaurus which can represent the selected compound concept, indexer should try to express it through the combination of two or more simple descriptors.

6. Use geographical descriptors

If the geographical context of a document is clearly mentioned or a document deals specifically with a country, region or an international organization, use thesaurus geographical descriptors.

7. Indexing should not concern the physical entity of the document

Type of document, author or any other metadata which do not concern the content of the document should not be indexed with thesaurus terms. This information is covered by other metadata.

8. Achieve indexing consistency

Within a large indexing team, a centralized checking stage is recommended to be set up and the creation of flexible templates can be good solutions for achieving indexing consistency.

<cdm:work_is_about_concept_eurovoc rdf:resource="http://eurovoc.europa.eu/3526"/>

PART II: Applying the general indexing principles: concrete rules and examples from the already indexed EUR-Lex documentary collection

1. Use EuroVoc for indexation and the Directory code and Subject headings for classification

While indexing with EuroVoc, indexer should keep in mind the different purpose and the use of an indexing tool and a classification tool.
The systematic use of general EuroVoc terms (most frequently top terms) can easily result in classifying the documents instead of indexing them, so their use should be limited to documents at very general level and only to documents that really speak about the selected general descriptor.
This principle is in line with the principle that the most specific EuroVoc term should be used. Before assigning a general term (top term) to a document, indexer is asked to examine whether one of its specific term corresponds better to the content of the document.
Classifying instead of indexing may occur not only at top terms level but at specific level as well. To avoid this, indexer is always asked to verify before assigning a descriptor to a document whether the chosen descriptor really corresponds to the content of the document (indexation) or only classifies the document by referring to its main subject(s) (classification).

i) 32011D0302: Council implementing decision 2011/302/CFSP concerning restrictive measures against Syria
This document concerns in general the common foreign and security policy. In this case the descriptor CFSP was used to classify the document (see classification under the Directory code and Subject mater):

EUROVOC descriptor:
international sanctions / human rights / CFSP / restriction of liberty

Directory code:
18.00.00.00 Common Foreign and Security Policy

Subject matter:
Common foreign and security policy

ii) 32011D0019(01): Decision of the European Central Bank of 15 November 2011 amending Decision ECB/2007/7 concerning the terms and conditions of TARGET2-ECB (ECB/2011/19)
This document concerns in general the European Monetary Union. In this case the descriptor Economic and Monetary Union was used to classify the document (see classification under the Directory code and Subject mater):

EUROVOC descriptor:
Economic and Monetary Union / electronic banking / intra-Community payment

Directory code:
10.30.30.00 Economic and monetary policy and free movement of capital / Economic policy / Economic and monetary union

Subject matter:
Economic and Monetary Union, European Central Bank, Euro

2. Follow the three stages of indexing

If the three intellectual stages of the indexation process are not respected, it may lead to some typical indexation errors and may negatively affect the performance of the query.
These errors are the followings:

A. Missing descriptors
If descriptors are missing, the query system will not retrieve the relevant documents answering to the users' query. There will be an information loss or 'silence' and desscriptor has to be added.

Missing descriptors occurs due to imperfection:
• either in identification of the essential concepts with a potential value for the users during document analysis
• or in translation of these identified concepts into EuroVoc descriptors

If there is no descriptor in EuroVoc corresponding to the selected concept (neither at the same level of specificity, nor at the next higher level), indexer should try to represent the given concept by the combination of several existing descriptors.
If it is not possible, propositions can be sent to the OP by using the 'Contribute' menu of the EuroVoc website in order to include a new descriptor in EuroVoc.

i) 2011CN0414: Reference for a preliminary ruling from the Polimeles Protodikio Athinon (Greece) lodged on 8 August 2011
This document concerns questions, which should be clarified by the Court of Justice: "Under Article 27 of the TRIPS Agreement are chemical and pharmaceutical products patentable subject matter provided that they satisfy the requirements for the grant of patents and, if so, what is the scope of their protection?"

Descriptor TRIPS – the main descriptors which should be used to cover the subject of the document – was missing:

EUROVOC descriptor:
European patent / patent law / chemical product / pharmaceutical product

ii) 32011R1004: Commission Implementing Regulation (EU) No 1004/2011 of 11 October 2011 amending the representative prices and additional import duties for certain products in the sugar sector fixed by Implementing Regulation (EU) No 971/2011 for the 2011/12 marketing year
One of the main descriptors ("representative price") was missing:

EUROVOC descriptor:
Community import / raw sugar / CCT duties / beet sugar / cane sugar

iii) 32011D0634: Council Decision of 17 May 2011 on the signing, on behalf of the European Union, and provisional application of the International Cocoa Agreement 2010
• One of the main descriptors ("signature of an agreement") was missing.
• If a document concerns an agreement, also the type and the field (EC trade agreement) of the agreement should be expressed by indexing terms – see also Annex III (Descriptors clarification), EC agreement.

EUROVOC descriptor:
sustainable development(*) / economic growth(*) / cocoa
(*) In this case too general descriptors were used. See point 2.3 (Be as specific as possible).

B. Incorrect descriptors
If descriptors are incorrectly used (not relevant, out of context), the query system will retrieve several but irrelevant documents, there will be a 'noise'  In that case, incorrect descriptors have to be deleted.

The use of incorrect descriptors is due to:
• either the misunderstanding of the content of the document
• or to the defect in examining the contextual and semantic environment of the selected descriptor (non-preferred terms, related terms, hierarchy, notes) which may lead to the misunderstanding of the selected descriptor

Theoretically, the semantic environment of a descriptor helps to clarify the meaning of a descriptor, but if it is not the case, clarification and additional notes to a EuroVoc term can be demanded from the OP.

i) 620091TA00118: Case T-118/09: Judgment of the General Court of 5 October 2011 — La Sonrisa de Carmen and Bloom Clothes v OHIM — Heldmann (BLOOMCLOTHES)

EUROVOC descriptor:
real estate business / European trademark / registered trademark

This document concerns the trademark law. The subject of commercial activity of the companies – parties to the action – is not specified in the text. Anyway, the name of the trademark in question (Blomclothes) could indicate the field of the business activity – clothing. For more information a more detailed searching is needed in this case (related documents, web sites of the companies etc.).

ii) 52011XC1011(04): Commission communication pursuant to Article 17(5) of Regulation (EC) No 1008/2008 of the European Parliament and of the Council on common rules for the operation of air services in the Community

EUROVOC descriptor:
public servi / invitatice / invitation to tender / inland transport / air transport /Greece

This document concerns an invitation to tender for providing service of general interest (air transport). The descriptor "public services" refers to "the body providing a service" (see SN). Descriptor "services of general interest" should be used in this case.

iii) 52011DC0666: Communication from the Commission to the European parliament and the Council: Enlargement Strategy and Main Challenges 2011-2012

EUROVOC descriptor:
Albania / Community acquis / Turkey / ISPA / accession criteria / Macedonia

Macedonia is a region of Greece. This communication concerns the "Former Yugoslav Republic of Macedonia".

3. Be as specific as possible

According to the general indexing principle, the most specific EuroVoc term should be selected.
If a document is indexed at a higher/more general level than the level of specificity of the selected concept, it will generate ‘noises’ and user will get irrelevant results.

i) 32011D0739: Council Decision of 20 October 2011 on the conclusion of the Agreement between the European Union, the Swiss Confederation and the Principality of Liechtenstein amending the Additional Agreement between the European Community, the Swiss Confederation and the Principality of Liechtenstein extending to the Principality of Liechtenstein the Agreement between the European Community and the Swiss Confederation on trade in agricultural products

EUROVOC descriptor:
Liechtenstein / foodstuff / EC agreement / designation of origin / Switzerland / agricultural product / ratification of an agreement

The more specific descriptor "EC trade agreement" should be used in this case. "EC agreement" and "EC trade agreement" belongs to the same hierarchical line. "EC trade agreement is the NT of 'EC agreement".

ii) 62006FB0105: Case F-105/06: Order of the Civil Service Tribunal (First Chamber) of 27 September 2011 — Lübking and Others v Commission
The case concerns: "Annulment of the Commission’s decision published in Administrative Notices No 85 2005 of 23 November 2005 in so far as it provided for promotion of the applicants to grade A*9 and not grade A*10 in the 2005 promotion exercise."

EUROVOC descriptor:
equal treatment / appointment of staff / professional career / staff assessment / European official

The more specific descriptor "promotion" should be used in this case. "Professional career" and "promotion" belong to the same hierarchical line. "Promotion" is the NT of "Professional career".

iii)32011R1136: Commission Implementing Regulation (EU) No 1136/2011 of 9 November 2011 establishing the standard import values for determining the entry price of certain fruit and vegetables

EUROVOC descriptor:
fruit / Community import / vegetable / import price / common organisation of markets

Ephemeral documents usually contain (in their annexes) the concrete product names or the Combined Nomenclature (CN) codes of the products concerned by the act. Indexer is asked to use the most specific descriptor corresponding to the products and not only descriptors referring to the category of the concerned products. More specific descriptors (citrus fruit, grape, pip fruit and fruit vegetable) should be used in this case.

If EuroVoc has no descriptor at the same level of specificity as the selected concept, the descriptor at the next higher level should be chosen: Commission Implementing Regulation (EU) No 388/2011 of 19 April 2011 concerning the authorisation of maduramicin ammonium alpha as a feed additive for chickens for fattening (holder of authorisation Alpharma (Belgium) BVBA) and amending Regulation (EC) No 2430/1999 Text with EEA relevance: Since EuroVoc has no descriptor for ‘maduramicin ammonium’ (which is an antibiotic), use the descriptor at the next higher level.

In some cases, specific terms are considered in EuroVoc as non-preferred terms of generic terms. (e.g. name of classes and their components – reptile NPT crocodile)

4. Simultaneous use of several descriptors belonging to the same hierarchical line

Before indexers select a Eurovoc term, they should navigate the content of the thesaurus and analyze the hierarchical relationships of the selected terms. It will alert them to the existence of a more or a less generic term belonging to the same hierarchical line: if both of them suits to the content of the document, the most specific one should be used.

i) 32011R0418: Commission Implementing Regulation (EU) No 418/2011 of 28 April 2011 amending the representative prices and additional import duties for certain products in the sugar sector fixed by Regulation (EU) No 867/2010 for the 2010/11 marketing year

EUROVOC descriptor:
sugar product / syrup / representative price / CCT duties
Descriptors sugar product and syrup belong to the same hierarchical line. The most specific should be chosen.

ii) 62011CN0454: Reference for a preliminary ruling from the Latvijas Republikas Augstākās tiesas Senāta Adminsitratīvo (Republic of Latvia) lodged on 1 September 2011 — Gunārs Pusts v Lauku atbalsta dienests

EUROVOC descriptor:
aid recipient / terms of aid / aid system
Descriptors aid recipient and aid system belong to the same hierarchical line. The most specific should be chosen.

5. Prefer pre-coordinated descriptors to ‘simple’ descriptors or to the combination of two or more ‘simple’ descriptors

EuroVoc, originally built up specifically for processing the documentary collection of the EU institutions, contains a large number of pre-coordinated descriptors in the field of EU activities. These pre-coordinated descriptors (e.g. ‘import (EU)’) exist in parallel with ‘simple’ descriptors (e.g. ‘import’), either with a hierarchical relationship between them (same hierarchical line) or as related terms, belonging to different top terms or microthesauri.
Giving preference to the use of pre-coordinated EuroVoc descriptors is essential since it affects the performance of the query results.
In EUR-Lex, there are an important number of documents that requires pre-coordinated descriptors. If EuroVoc does not contain the necessary pre-coordinated descriptor, propositions can be sent to the OP via the Contribute menu of Euro.

Examples of pre-coordinated descriptors:
appointment of staff (in general, BT personnel administration). Do not use this descriptors for indexing a document about the appointments in EU institutions/bodies Ex: 32011D0243
appointment of members – pre-coordinated – use only for the appointments in EU institutions, bodies, agencies

budget financing – resources of a budget (national budget, budget of an organisation, etc.)
financing of the EU budget – pre-coordinated – concerns the different types of resources of the EU (Where does the money come from? How is EU budget is financed?)

import Ex: 32011R0385
import (EU) pre-coordinated

export Ex: 52011PC0245
export (EU) pre-coordinated

bilateral agreement – See SN – use for documents about agreement between two States Ex: 52011SC0640
EC agreement – pre-coordinated – use for documents about agreement between the EU in one part + third country or (international) organisation in combination with the country name or the organisation's name. If possible, use specific pre-coordinated descriptors for the different types of EU agreements (European association agreement, association agreement (EU), cooperation agreement (EU), interim agreement (EU), trade agreement (EU), negotiation of an agreement (EU)) EX: 32011D0334

action programme – BT management (UF framework programme, plan of action, work programme) Do not use for EU programmes Ex: 52011AE0533
EU programme – pre-coordinated

6. Use geographical descriptors

Domain 72 Geograpy of EuroVoc contains geographical descriptors. Use descriptors of countries when a document concerns specifically one or more countries or examines a particular situation in a given country. For example:
• agreement with a country
• action against a State / judgment of a court concerning a country
• national statistics
• state aid regime of a country / authorization of State aid, etc.
• EU financing expenditure in a State
• origin of a product
• national law of a State

Group of countries / international organisations
If the document speaks about group of countries or international organisations as a whole, do not list the name of the member countries, but use only the descriptor concerning the group from the domain 76 International organisations.
However, if needed, country names and descriptors referring to an organisation/group of country can be used simultaneously since they do not belong to the same hierarchical line and domain.

52010XG0415(01): Notice for the attention of the persons, entities and bodies to which restrictive measures provided for in Council Decision 2011/239/CFSP apply

EUROVOC descriptor:
international sanctions / economic sanctions / natural person
A geographical descriptor is missing (Myanmar). Restrictive measures are provided against Burma/Myanmar.

Regions
Only the names of regions of EU Member States are in EuroVoc, but not those of third countries.
Use regions' names when a document is specifically about a region of an EU Member State.
If needed, regions names can be used together with country names since they do not belong to the same hierarchical line.

52010X0416(03): Summary information communicated by Member States on State aid granted

EUROVOC descriptor:
Italy / fishing industry / aid system / control of State aid / small and medium-sized enterprises / aquaculture / State aid
A geographical descriptor is missing (Sardegne). State aid was granted by the 'Regione Autonoma della Sardegna'.

7. Physical entity of the document

Indexation of the EUR-Lex documentary collection with EuroVoc should not concern the type and/or the author of the document. This information are covered by other metadata, EuroVoc descriptors should be only used to index the content of the document.

Author
The use of ‘institutions’ descriptors (EU institutions, bodies, services, organisations, agencies and international organizations) should be limited to documents which are about:
• the functioning of an institution (rules of procedures, composition, appointment, etc.)
• the competencies of an institution
• the role of an institution
• the activity of an institution
• agreements, cooperation between institutions

Do not use ‘institutions’ descriptors of EuroVoc when the given institution or body is the author of the document and the document does not speak about its functioning, activity, etc.

52011SC0622): Commission staff working paper accompanying the report from the Commission to the European parliament and the Council

EUROVOC descriptor:
Community financing / EC Commission / information

Author:
European Commission

Descriptor EC Commission refers to the author of the document. This descriptor should be deleted.

Type of document/of act
EuroVoc descriptors belonging to the top term ‘document’ or to ‘EU act’ should not be used for identifying the type of document. Other field of metadata is available for that purpose.

52010XX1016(01): Opinion of the European Data Protection Supervisor on Promoting Trust in the Information Society by Fostering Data Protection and Privacy

EUROVOC descriptor:
data processing / personal data / Community opinion / European data protection supervisor

Form:
Opinion

Descriptor Community opinion refers to the type of the document. This descriptor should be deleted.

Type of procedure/parties (case-law)
Descriptors referring to the nature of the proceeding, to the parties of proceeding (applicant, defendant) etc. should not be used. This information is covered by other metadata (PR).

62008TA0449: Case T-449/08: Judgment of the General Court of 18 October 2011 — SLV Elektronik v OHIM — Jiménez Muñoz (LINE)

EUROVOC descriptor:
European trademark / trademark law / action for annulment of an EC decision / lighting equipment

Type of procedure:
Action for annulment - successful

Descriptor action for annulment of an EC decision refers to the type of the procedure. This descriptor should be deleted.

8. Achieve indexing consistency

Concerning the EUR-Lex documentary collection, the creation of flexible templates can be good solutions for achieving indexing consistency. The indexing terms in these templates may change according to the content of the document.
Already defined templates are listed in the third part of the document.

Subject matter is a classification tool containing alphabetically structured list of over 200 keywords. It is based on the subdivisions of the treaties and on the areas of activity of the institutions. The descriptors are less specific than those used in the Directory code but provide a general overview of the content of the document.

Classification of a document by using of Subject matter descriptors must be based on the analysis of the content of the document.

The list of descriptors covers the chapters of the treaties and areas of EU activities. This classification is rather general, it becomes more specific in the areas of agricultural and customs duties.

If a document refers to more areas of EU policies, all those areas must be indexed by using of Subject matter descriptors.

Sometimes more general descriptors appear alongside more specific descriptors, but in generally the descriptors attributed must be as specific as possible. The maximum number of descriptors to be used is 3.

Subject matter is a classification tool. The content of document is usually more completely described by EuroVoc descriptors.

In order to maintain consistency, some rules must be respected by the indexation:

For modifying documents, the same descriptors should be used as for the modified document.

For documents related to the anti-dumping – commercial policy and dumping should be always used.

For legislation adopted on a legislative proposal, use the descriptors form the proposal.

For agreements adopted by decision of the Council, use the same descriptors as in the act adopting the agreement.

For documents concerning the budget use budget.

For directives, use also approximation of laws.

<cdm:resource_legal_is_about_subject-matter rdf:resource="http://publications.europa.eu/resource/authority/fd_070/UD"/>

EU Case law directory code is a specific directory classification for EU case law.

There are two different version of the EU case law directory:

– before 2010 (RJ)
– after 2010 (RJ_NEW) – this directory follows the changes brought up by the Lisbon Treaty

The analysis is provided by the Court of Justice of the European Union.

<cdm:case-law_is_about_concept_new_case-law rdf:resource="http://publications.europa.eu/resource/authority/fd_578/3.02.00"/>

Most important properties from the legal analysis point of view

The Author field indicates the name of the institution, the body or the country that produced the act.

Check the title of the act and consult the values used in relevant templates (or values attributed to similar documents in the past).

When possible (for example acts of the European Commission, European Parliament, EESC, CoR) the field also contains the name of the committee or the competent section.

EU treaties and international agreements: name of the country (countries) signing a treaty or an agreement should be indicated.

<cdm:work_created_by_agent rdf:resource="http://publications.europa.eu/resource/authority/corporate-body/EP"/>

If there are no concepts available for different association/cooperation councils or joint committees in the relevant NAL corporate-body (as for example EU – Republic of Moldova Association Council), please use a combination of more generic concepts (Association Council – COUN_ASS, Cooperation Council – COUN_COOP, Joint Committee – CMT_CONJOIN etc.) together with the country name (codes coming from corporate-body + country).

April 2015: For parliamentary questions, the author field contained also the name of the Member of the European Parliament in the past. However, because of missing mapping in the CELLAR, those names are currently not displayed on the new EUR-Lex. Possible solutions should be analysed.

<rdf:Description rdf:nodeID="A2">
<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Axiom"/>
<annot:build_info>cdm:CDM_2.1.7 tdm:1523 xslt:3945 saxon:9.0.0.1J JVM:1.6.0_29 metaconvJar:1.1.9 builddate:06/12/2013 15:38:22</annot:build_info>
<annot:quality_issue>DATWRO</annot:quality_issue><annot:error_message>Data wrong</annot:error_message>
<annot:old_value>Urszula Gacek</annot:old_value>
<owl:annotatedSource rdf:resource="http://publications.europa.eu/resource/celex/92009E000068"/><owl:annotatedTarget rdf:resource="http://publications.europa.eu/resource/authority/corporate-body/OP_DATPRO"/><
owl:annotatedProperty rdf:resource="http://publications.europa.eu/ontology/cdm#work_created_by_agent"/>
</rdf:Description>

10/07/2015: Author to be used in 22015D0921: Decision No 1/2015 of the EU-EFTA Joint Committee on Common Transit of 11 May 2015 concerning an invitation to the former Yugoslav Republic of Macedonia to accede to the Convention on a common transit procedure [2015/921]

Codes referring to EC-EFTA Joint Committee and EEC-EFTA Joint Committee were deprecated in corporate bodies table and there is no successor referring to EU-EFTA Joint Committee.

In such case, the values referring to the Joint Committee (CMT_JOIN), European Union (EURUN) and EFTA (EFTA) should be used.
If the horizontal structure of the corporate bodies will be implemented in Cellar and EUR-Lex, value EURUN will not be needed anymore in this case as it is a parent value of CMT_JOIN.

12/11/2018: Change concerning personal names – they are currently in cdm:work_created_by_agent: Personal authors would be under contributed_by (https://webgate.ec.europa.eu/CITnet/jira/browse/CDM-52).
Another change concerning contributed_by cdm:work_contributed_by_agent is removed from the notice+index and only cdm:contributed_by will be indexed&in_notice (https://webgate.ec.europa.eu/CITnet/jira/browse/CDM-119).

21/10/2019: Personal names present in cdm:work_created_by_agent for fd_013 in documents from sector 9 could be also moved to cdm:asked_by. Check https://webgate.ec.europa.eu/publications/jira/browse/CADMOS-7932

This field refers to the type of act. The type is usually indicated in the title of an act. However, the value used in Type of act might not be the same as the one used in the title, as this metadata shall describe the document type in legal terms.

Check the title of the act and consult the values used in relevant templates (or values attributed to similar documents in the past).
There should be only one value attributed except of corrigenda where two different values shall be used: (1) corrigendum and (2) the same value as available in the corrected act.

< cdm:work_has_resource-type rdf:resource="http://publications.europa.eu/resource/authority/resource-type/REG_IMPL"/>

April 2015: For the time being, both properties cdm:work_has_resource-type as well as cdm:resource_legal_has_type_act_concept_type_act shall be used because of technical reasons. For the display and search purposes, only cdm:resource_legal_has_type_act_concept_type_act is currently used by the EUR-Lex.

In few months, a complete switch to cdm:work_has_resource-type will be done.

18/09/2015: Correction related to DECBES value: https://webgate.ec.europa.eu/publications/jira/i#browse/LAAION-44

Indicator for the extraction of titles for the production of the Directory.
This field indicates whether an act is basing (containing anonomous provisions) or amending (not containing antonomous provisions and just amending previous act(s)).

This field has to be used for legislative and non-lagislative acts as well as for proposals of such acts.

There are three possible values:

REP – appears in the Directory with a full title
LIE – appears in the Directory as a reference
CADUC – stricken from the Directory (documents which should no more appear in the directory; to be used for special cases and only when requested)

The field is mandatory for legislation, agreements and proposals.

Basic legislative act must be indexed with REP. Acts amending the basic acts should be indexed with LIE.

Basic acts appear in the directory with the title, amending acts only as a links to the related basic acts.

For amending acts containing also autonomous provisions: It is not possible to index one document with both descriptors REP and LIE, only LIE should be used. The reference to the amending act will be still present in the directory (as link from the basic act to the amending one).

Corrigenda, ephemeral acts and acts whose only content is the repeal of a basic act should not be indexed, neither with REP nor with LIE.

<cdm:resource_legal_repertoire rdf:datatype="http://www.w3.org/2001/XMLSchema#string">REP</cdm:resource_legal_repertoire>

Join practical guide (2015; ISBN 978-92-79-49121-4; ISBN 978-92-79-49084-2) – Amending acts without autonomous provisions and basic acts with amending provisions

8.3. The title of an act amending earlier acts is a special case. The title is incomplete unless it refers by number to all the acts amended. Without such a reference, it is not possible to find all the amendments to a given act. If the sole purpose of the act in question is to amend another act, either the sequential reference number and title of the act to be amended or its sequential reference number and the specific purpose of the amendment is mentioned (see points 18.9 and 18.10). In contrast, if the act in question lays down autonomous provisions and consequently amends another act in a purely subsidiary manner, only the number of that act is given (see point 19.3).

19. An act not primarily intended to amend another act may set out, at the end, amendments of other acts which are a consequence of changes which it introduces. Where the consequential amendments are substantial, a separate amending act should be adopted.

19.1. Sometimes an act with autonomous provisions alters the legal context of a given field to such an extent that other acts governing other areas within the same field need to be amended. To the extent that the amendment is only secondary to the main scope of the act, the juxtaposition of autonomous and amending provisions in the same act does not fall within the prohibition set out in Guideline 18 on the inclusion of autonomous substantive provisions in amending acts.
In order for the amendment to be apparent, it must be mentioned in the title of the act, by stating the sequential reference number of the act to be amended (see point 8.3).
Example:
Council Directive 92/96/EEC of 10 November 1992 on the coordination of laws, regulations and administrative provisions relating to direct life assurance and amending Directives 79/267/EEC and 90/619/EEC

04/11/2019: Check basic acts containing "amending" at the end of the title; many of them could be indexed with LIE

18/2/2019: Discussion with AION regarding Join practical guide, points 8.3 and 19
REP: Autonomous act containing "subsidiary" amendments (32005R0396 or 31992L0096). At the end of the title, “amending” can be found.
LIE: Amending acts containing "subsidiary" autonomous provisions, it seems to be just a theoretical example. The title of such act contains its number and document date which are directly followed by “amending”.

Indicator whether a piece of legislation still in force or not in force.

In force indicator is applicable only to certain acts (EU legal acts - legislative and non-legislative acts, treaties, international agreements plus some other cases).

This field is generated automatically, based on the end of validity date and date of effect. Values are true or false.

If there is at least one IF ≤ TODAY and at least one EV ≥ TODAY is present in the notice, true is inserted.
If date of entry into force is not yet known (0001-01-01; e.g. cases where it is linked to the date of notification), false is inserted.

Ephemeral notices are excluded (value EPH present in manifestation_official-journal_part_durability):
<cdm:manifestation_official-journal_part_durability rdf:datatype="http://www.w3.org/2001/XMLSchema#string">EPH</cdm:manifestation_official-journal_part_durability>

For acts entering into force in the future, the value is false.

<cdm:resource_legal_in-force rdf:datatype="http://www.w3.org/2001/XMLSchema#boolean">true</cdm:resource_legal_in-force>

04/11/2019: GIL-GM Acts annuled by CdJ decision - VV field - proposal to be prepared
The legal analysis methodology does not follow up on the annulments of legal acts by judgments of the Court of Justice. Currently the date of end of validity of those acts remains indefinite; therefore, they remain marked as 'in force'.

The Commission Legal Service was consulted and considered that the effect should be as if it had never existed, therefore the value contained in the date of effect field should be reproduced in the date of end of validity, and the in force indicator switched to 'not in force'. The participants agreed on this solution and indicated that the comment 'declared void by' should be shown below the title, next to the in force indicator coloured point.


This solution should also be applied to cases where the judgment annuls the decision but orders to maintain the effects of the decision in force.

11/03/2019: Display of VV on EUR-Lex - There were new values created on EUR-Lex "Not yet in force". Rules:
VV=true: "In force"
VV=false AND EV>TODAY: "Not yet in force" (expert search VV2=NOT_YET_IN_FORCE)
VV=false AND EV<TODAY: "No more in force" (expert search VV2=NO_MORE_IN_FORCE)

VV is not displayed when there is a date of notification=01/01/1001 (see: NF=01/01/1001 AND VV=false ORDER BY XC DESC)

Additional properties relevant for the legal analysis

The treaty field contains the name of the treaty/treaties that form the legal basis under which the document has been adopted. This field is linked to the Treaties authority table; no CELEX numbers are used.

The name of the treaty/treaties that form the legal basis is mentioned in the text (visa of legislative act).

<cdm:resource_legal_based_on_concept_treaty rdf:resource="http://publications.europa.eu/resource/authority/treaty/TEU_2012"/>

04/11/2019: Property cdm:resource_legal_based_on_treaty was used in the past, it has been depricated and replaced by
cdm:resource_legal_based_on_concept_treaty

The Commission DG or DGs, author of a Commission proposal.

The fields contain codes corresponding to the acronyms of the Commission DG's. The source is list of acronyms for the DGs of the Commission (see Inter-institutional Style Guide point 9.6) or corporate body authority table.
In addition to acronyms (made up of letters, derived mainly from the FR) the old DG numbers were used for the documents of the time before the restructuring.
The source to be used is legislative procedure (Leading service - cdm:event_legal_responsibility_of_institution; Joint leading service - cdm:event_legal_joint-responsibility_of_institution). In some cases, this information can be found in the text. Another source might be Vista. (Vista is an internal system for Commission staff. It offers an overview of the Commission decision-making process. It gives access to non-classified Commission documents and to related procedural information.)

cdm:proposal_act_service_responsible rdf:datatype="http://www.w3.org/2001/XMLSchema#string">SANCO</cdm:proposal_act_service_responsible>

04/11/2019: Check cdm properties, which are still used?

04/11/2019: Author field also contain name of responsible DG. In such cases RS just duplicates this information. Check how it is treated in IMMC.

cdm properties:
*cdm:proposal_act_service_responsible (deprecated: CDM-75 https://webgate.ec.europa.eu/publications/jira/browse/EURLEXNEW-3413)
*cdm:non-opposition_concentration_notified_service_responsible
*cdm:non-opposition_joint-venture_notified_service_responsible
*cdm:regulation_service_responsible
*cdm:decision_service_responsible
*cdm:directive_service_responsible
*cdm:document_com_other_ec_service_responsible
*cdm:act_legislative_other_oj_c_service_responsible
*cdm:act_legislative_other_oj_l_service_responsible
*cdm:staff-working-document_service_responsible
*cdm#resource_legal_service_responsible
*cdm#resource_legal_responsibility_of_agent

This field contains general miscellaneous information that varies greatly according to the type of document and EUR-Lex sector.

Miscellaneous information is used to index a range of information not provided for in other EUR-Lex fields and is optional for all EUR-Lex documents. Some of the most frequently found types of information indexed in Additional information are listed below.

The validity and notice of termination information in international agreements (Sector 2).
The NACE classification code data in Merger Task Force decisions (Sector 3).
Additional information on the period of validity. For legislation (end of season, end of financial year) and agreements (validity).
Numerous mentions including EEA relevance, Directive amending date of transposition not specified in the directive and Directive amending may be indexed in the additional information field of directives (Sector 3).
The remark Parliament consulted by document No followed by a reference, date, type of legislative procedure and other details are often found in preparatory documents (Sector 5).
The CELEX number of joined cases for decisions of the European Courts (Sector 6).
The CELEX number of the directive or ECSC recommendation concerned by the Member States’ national provisions (Sector 7).

<cdm:resource_legal_information_miscellaneous rdf:datatype="http://www.w3.org/2001/XMLSchema#string">JOIN 2014/0034</cdm:resource_legal_information_miscellaneous>

Judgment of the Court of 14 December 2000 Parfums Christian Dior SA v TUK Consultancy BV and Assco Gerüste GmbH and Rob van Dijk v Wilhelm Layher GmbH & Co. KG and Layher BV.
References for a preliminary ruling: Arrondissementsrechtbank 's-Gravenhage and Hoge Raad der Nederlanden - Netherlands.
Agreement establishing the World Trade Organisation - TRIPs Agreement - Article 177 of the EC Treaty (now Article 234 EC) - Jurisdiction of the Court of Justice - Article 50 of the TRIPs Agreement - Provisional measures - Interpretation - Direct effect.
Joined Cases C-300/98 and C-392/98
European Court Reports 2000 Page I-11307

Additional information:
Joined case : 698J0392

Council Regulation (EC) No 198/2001 of 29 January 2001 amending the Annex to Regulation (EC) No 2042/2000 imposing a definitive anti-dumping duty on imports of television camera systems originating in Japan

Additional information:
Dumping

Partnership agreement between the members of the African, Caribbean and Pacific Group of States of the one part, and the European Community and its Member States, of the other part, signed in Cotonou on 23 June 2000

Additional information:
Validity: notice of termination of 6 months

Commission Decision of 15/12/2000 declaring a concentration to be compatible with the common market (Case No IV/M.2245 - METSÄ-SERLA / ZANDERS) according to Council Regulation (EEC) No 4064/89 (Only the English text is authentic)

Additional information:
NACE=DE.21.00

Amendment by France of public service obligations in respect of scheduled air services within France (Text with EEA relevance)

Additional information:
EEA relevance

2000/770/EC: Internal Agreement between Representatives of the Governments of the Member States, meeting within the Council, on the Financing and Administration of Community Aid under the Financial Protocol to the Partnership Agreement between the African, Caribbean and Pacific States and the European Community and its Member States signed in Cotonou (Benin) on 23 June 2000 and the allocation of financial assistance for the Overseas Countries and Territories to which Part Four of the EC Treaty applies

Additional information:
Validity: until adoption of definitive measures

This field indicates a co-author of a Commission proposal (Commission DG or DGs).

The fields contain codes corresponding to the acronyms of the Commission DG's. The source is list of acronyms for the DGs of the Commission (see Inter-institutional Style Guide point 9.6) or corporate body authority table.
In addition to acronyms (made up of letters, derived mainly from the FR) the old DG numbers were used for the documents of the time before the restructuring. The source o be used are legislative procedures (associated service - cdm:event_legal_associated_with_institution). In some cases, this information can be found in the text. Another source might be Vista. (Vista is an internal system for Commission staff. It offers an overview of the Commission decision-making process. It gives access to non-classified Commission documents and to related procedural information.)

<cdm:proposal_act_service_associated rdf:datatype="http://www.w3.org/2001/XMLSchema#string">MARKT</cdm:proposal_act_service_associated>

04/11/2019: Check cdm properties, which are still used?

cdm properties:
*cdm:proposal_act_service_associated (deprecated: CDM-75 https://webgate.ec.europa.eu/publications/jira/browse/EURLEXNEW-3413)
*cdm:regulation_service_associated
*cdm:directive_service_associated
*cdm:decision_service_associated
*cdm:document_com_other_ec_service_associated
*cdm:staff-working-document_service_associated
*cdm#resource_legal_service_associated

Internal reference used for sector 5 documents from EESC.

<cdm:resource_legal_position_eesc rdf:datatype="http://www.w3.org/2001/XMLSchema#string">AVIS-SECTION 2013/4522 FIN</cdm:resource_legal_position_eesc>

04/11/2019: Check how this field is used and whether it is needed or not. Check also IMMC.

Class or subclass according to CDM.

This field is most frequently used in Sector 2 where it contains the name of the depositary of an international agreement.

Depositary as indicated in the text. It might be state, government, institution or other organisation.

<cdm:treaty_stored_by_agent rdf:resource="http://publications.europa.eu/resource/authority/fd_040/I-G"/>

04/11/2019: Check cdm properties

04/11/2019: cdm properties:
*cdm:treaty_stored_by_agent
*cdm:legislation_complementary_stored_by_agent
*cdm:agreement_international_stored_by_agent

This field contains diverse data that have been added to facilitate the work of the units of the European Union.

Several comments and identification codes for management purposes.

Currently the following codes are used:

MAN0 - mise à niveau 0 (before 1995)
MAN1 - mise à niveau 1 (since 1995)
MAN2 - mise à niveau 2 (daily production)
MAN3 - mise à niveau 3 (since 1995 – amendments to repealed acts)
MAN4 - mise à niveau 4 (since 1998 – correction pagination)
INFO1 - Non-legal documentation
EPH - ephemeral documents (acts relating to day-to-day management of agricultural matters;titles of such acts are are printed in light type on the cover of OJ-L)

No other entries are allowed without prior authorisation.
This field has a free text format and the contents are exported without translation to the EUR-Lex dissemination databases.
Internal comment is currently not displayed on the EUR-Lex.

<cdm:resource_legal_comment_internal rdf:datatype="http://www.w3.org/2001/XMLSchema#string">MAN2</cdm:resource_legal_comment_internal>

04/11/2019: Check wheather this field and values MAN are still useful or not.

28/02/2017: New value for ephemeral documents introduced (EPH).

This field provides the date of the debate or the session for European Parliament resolutions, Economic and Social Committee and CR opinions and resolutions.

The number of session is usually indicated in the text.

<cdm:opinion_eesc_number_session rdf:datatype="http://www.w3.org/2001/XMLSchema#string">{SESSION|http://publications.europa.eu/resource/authority/fd_345/SESSION} 376</cdm:opinion_eesc_number_session>

12/12/2018: Changes in cdm proerties EURLEXNEW-3672 The following cdm properies shall be depricated:
*cdm:opinion_eesc_number_session
*cdm:act_other_cor_number_session
*cdm:act_other_eesc_number_session
*cdm:opinion_consultation_cor_number_session
*cdm:opinion_consultation_eesc_number_session
*cdm:opinion_other_cor_number_session
*cdm:opinion_other_eesc_number_session
*cdm:question_parliamentary_number_session

Where available this field contains the name of the State, institution, organisation or individual to whom the act is addressed (addressee of parliamentary resolutions; addressee of legislation in general, and MTF decisions in particular).
This field is applicable to European Parliamentary questions, resolutions and opinions, as well as for Merger Task Force decisions. It is also used to index Commission decisions.

Addressee parliamentary resolutions

The member states and/or other entities addressed by the European Parliament.
The field is used for parliamentary resolutions.

The field contains descriptors. The values permitted correspond to the codes of EUR-Lex Translation table 050.

The addressee of a legislative act, the entity to which the act is notified.
For acts addressed to all Member States: the field is remains empty.

The field is optional for legislation, but mandatory for MTF-decisions.

It always appears together with the field NF.

The field contains descriptors. The values permitted correspond to the codes of EUR-Lex Translation table 050.

<cdm:resource_legal_addresses_institution rdf:resource="http://publications.europa.eu/resource/authority/fd_050/CONS"/>

(13/07/2015): New code <LIBELLE CODE="CH">Switzerland</LIBELLE> was created in FD_050. Should be used also in this document: 32015D1056

(03/05/2016): Metadata field Addressee should not cover cases like Communications to the European Parliament and the Council or EP resolutions (to be forwarded to the Council, Commission and national parliaments).

(03/05/2016): CDM-135: In the context of merger cases, the Commission decisions declaring a concentration to be compatible with the common market concern two or more parties (usually companies). See an example https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:32017M8399 However, such values are currently stored as ‘Addressee’ (cdm:resource_legal_addresses_organization ) but this is not correct because these companies are only the object of the Commission investigation, and not the addressee of the decision. Therefore, it is necessary to create a new property which would store the names of these companies. Once this is created, the CELLAR team will have to move all the values from 'Addressee' into the new property.
The label for the new property should be : 'Companies involved".
The following new cdm property is going to be replaced (in_notice + to_be_indexed): cdm:resource_legal_involves_agent

04/11/2019: COUNTRY – see https://webgate.ec.europa.eu/publications/jira/browse/EURLEXNEW-3599, to be used for cdm:resource_legal_addresses_organization
cdm:resource_legal_addresses_country refers to the country being the addressee of an act while annotation COUNTRY refers to the "domicile" of the company being the addressee of an act…

04/11/2019: In EURLEXNEW-3713 AD should be linked to cdm#resource_legal_addresses_agent (proposed xpath */NOTICE/WORK/RESOURCE_LEGAL_ADDRESSES_AGENT/*)
when this will be done, more specific cdm#resource_legal_addresses_institution/organization/country could be removed from index+notice
The current ontology:
cdm:addresses
- cdm:resource_legal_addresses_agent (in_notice, to_be_indexed)
- - cdm:resource_legal_addresses_institution (in_notice, to_be_indexed)
- - cdm:resource_legal_addresses_organization (in_notice, to_be_indexed)
- - cdm:resource_legal_addresses_country (in_notice, to_be_indexed)

04/11/2019: Check cdm properties and pending changes:
*cdm:resource_legal_addresses_institution
*cdm:resource_legal_addresses_organization
*cdm:resource_legal_addresses_agent
*cdm:resource_legal_addresses_country

Link to related procedure (interinstitutional or internal). It contains the identificator of the procedure .

<j.0:work_part_of_dossier rdf:resource="http://publications.europa.eu/resource/procedure/2015_288"/>

Comments/additional details of international agreements and decisions taken by bodies created by these agreements.

Information about type of agreement, clause, declaration or about body/bodies created by the agreement.

The field is mandatory for agreements and optional for decisions of bodies created by these agreements. For the latter case, if the content to be displayed has already been included in other field (such as AU, FM…), then it will remain empty.

The field contains descriptors. The values permitted correspond to the codes of EUR-Lex Translation table FD_301.

<cdm:agreement_international_has_type_comment_concept_type_comment rdf:resource="http://publications.europa.eu/resource/authority/fd_301/ACC%2FMIXTE"/>

04/11/2019: Check how this field is used and whether it is needed or not. Check also IMMC.

This field contains a name of the person (EP member or member of CoR or EESC) who reports on the relevant act.

The name of the rapporteur-general, rapporteur or Member of the European Parliament (MEP) is usually written in the text. As a general rule only surnames of Members of Parliament are entered in the author field. First names are added to distinguish between two or more entries under the same name.

<cdm:resolution_legislative_ep_reported_by_person rdf:resource="http://publications.europa.eu/resource/authority/fd_013/CAPOULAS_SANTOS"/>

04/11/2019: cdm properties
*cdm:resolution_legislative_ep_reported_by_person
*cdm:document_budget_ep_reported_by_person
*cdm:resolution_legislative_ep_reported_by_person
*cdm:resolution_other_ep_reported_by_person
*cdm:decision_internal_ep_reported_by_person
*cdm:act_other_ep_reported_by_person
*cdm:opinion_consultation_eesc_reported_by_person
*cdm:opinion_other_eesc_reported_by_person
*cdm:opinion_eesc_reported_by_person
*cdm:act_other_eesc_reported_by_person
*cdm:opinion_consultation_cor_reported_by_person
*cdm:opinion_other_cor_reported_by_person
*cdm:act_other_cor_reported_by_person

04/11/2019: check cdm properties

This field indicates the authentic language version of an act or a European Court case. It indicates also the language of the corrigenda (this is applicable only from April 2015).

The languages indicated as authentic in the document.

For document authentic in all official languages, the field remains empty.

This field is relevant also for the communications on EU case law and corrigenda.

<cdm:resource_legal_uses_originally_language rdf:resource="http://publications.europa.eu/resource/authority/language/SPA"/>

This field refers to the political affiliation and nationality of the Member of the European Parliament who asked the question.
(Political groups represent various political tendencies within the Parliament. Each is represented in the Conference of Presidents by its chairperson, who also has the task of explaining the group’s position on issues under discussion at plenary sessions).

The political group is mentioned in the text.

<cdm:question_parliamentary_asked_by_group_parliamentary rdf:resource="http://publications.europa.eu/resource/authority/fd_290/FRACTIO-09%2F004"/>

This field concerns documents emanating from the European Parliament, specifically EP questions (Sector 9) and resolutions (Sector 5).

The field indicates the Parliamentary term during which the resolution was voted or the question was raised.

The descriptors currently used to index this field are: first legislature / second legislature / third legislature / fourth legislature / fifth legislature / sixth legislature / seventh legislature.

This field was introduced during the first legislature, i.e. the first universally elected Parliament (1979). This field is not available for earlier acts.

<cdm:question_parliamentary_term_parliamentary rdf:datatype="http://www.w3.org/2001/XMLSchema#string">7</cdm:question_parliamentary_term_parliamentary>

04/11/2019: Check the values used in this field
FD_285
n.a. (#string) However, only codes are exposed (not decoded), so 01, 02, etc.

30/11/2015: A new concept for the 8th parliamentary term was created in FD_285 (L-08 Eighth legislature) and published in MDR publication 20151118-0 (release date: 18/11/2015). Provisional value OP_DATPRO should be removed and replaced by L-08.

Properties applicable only to case-law collection

This field is relevant for announcements on EU case law published in the Official Journal. It refers to the defending institution, body or Member State. If the defendant is a private entity or person, then it, she or he is referred to as "person".

Defendant as indicated in the title of sector 6 documents or in the text:

Action brought on 16 August 2019 – Micreos Food Safety v Commission (Case T-568/19)
(2019/C 372/33)
Language of the case: English
Parties
Applicant: Micreos Food Safety BV (Wageningen, Netherlands) (represented by: S. Pappas, lawyer)
Defendant: European Commission

This field is not applicable to preliminary rulings.
Information about applicant or defendant is present also in the alternative title (NOM_USUEL).

<j.0:communication_cjeu_defended_by_agent rdf:resource="http://publications.europa.eu/resource/authority/fd_110/IC"/>

This field is relevant for announcements on EU case law published in the Official Journal. It refers to the institution, body or Member State submitting the application (EU case-law). If the applicant is a private entity or person, then it, she or he is referred to as "person".

Applicant as indicated in the title of sector 6 documents or in the text:

Action brought on 16 August 2019 – Micreos Food Safety v Commission (Case T-568/19)
(2019/C 372/33)
Language of the case: English
Parties
Applicant: Micreos Food Safety BV (Wageningen, Netherlands) (represented by: S. Pappas, lawyer)
Defendant: European Commission

This field is not applicable to preliminary rulings.
Information about applicant or defendant is present also in the alternative title (NOM_USUEL).

<j.0:communication_cjeu_requested_by_agent rdf:resource="http://publications.europa.eu/resource/authority/fd_110/PART"/>

This field is relevant for EU case law and national case law. It is not relevant for announcements on EU case law published in the Official Journal. It shows the country of origin of the applicant, the defendant or the court referring the case (EU case-law).

EU case law: The analysis is provided by CdJ.

This field is relevant for announcements on EU case law published in the Official Journal. This field contains a descriptor referring to the nature of and where possible the outcome of the proceedings.

The type of procedure is usually indicated in the title or in the text (here Action for annulment):

Form of order sought
The applicant claims that the Court should:
- annul the decisions of the Director General for Health and Food Safety of 17 June 2019, forming a unity, by which the Commission: a) definitively refrained from...

<j.0:communication_cjeu_has_type_procedure_concept_type_procedure rdf:resource="http://publications.europa.eu/resource/authority/fd_100/ANNU"/>

Description of some other editorial propereties used in this document

Field used in the cataloguing methodology for information purposes. It contains different comments related to the specific document type.

Field used in the cataloguing methodology for information purposes.

Field used in the cataloguing methodology for information purposes.

Field used in the cataloguing methodology for information purposes.

Field used in the cataloguing methodology for classification and search purposes. Keywords are usually extracted from the titles of documents.

The order among siblings under a common parent

EU treaties; celex sector 1

Agreements between EU (and its Memeber States) and third countries or international organisations; celex sector 2

22016A0311(01)
22012A0413(01)
22014A0611(02)
22014A0412(01)

Arrangement between the European Union and the Swiss Confederation on the modalities of its participation in the European Asylum Support Office

ARRANGEMENT entre l'Union européenne et la Confédération suisse sur les modalités de sa participation au bureau européen d'appui en matière d'asile

arrangement between EU and third country

DTS_SUBDOM = INTER_AGREE AND (TI~arrangement between) ORDER BY XC DESC

22016A0420(01)
22016A0421(01)
22014A0712(01)

Participation Agreement between the European Union and the Swiss Confederation on the participation of the Swiss Confederation in the European Union Advisory Mission for Civilian Security Sector Reform in Ukraine (EUAM Ukraine)

ACCORD DE PARTICIPATION
entre l'Union européenne et la Confédération suisse relatif à la participation de la Confédération suisse à la mission de conseil de l'Union européenne sur la réforme du secteur de la sécurité civile en Ukraine (EUAM UKRAINE)

Usually between EU and Swiss concerning CFSP

TI~"participation agreement" AND DTS_SUBDOM = INTER_AGREE ORDER BY XC DESC

22016A0521(01)
22019A0508(01)
22019A0426(01)

Protocol amending the Euro-Mediterranean Aviation Agreement between the European Union and its Member States, of the one part, and the Hashemite Kingdom of Jordan, of the other part, to take account of the accession to the European Union of the Republic of Croatia

PROTOCOLE
modifiant l'accord euro-méditerranéen relatif aux services aériens entre l'Union européenne et ses États membres, d'une part, et le Royaume hachémite de Jordanie, d'autre part, pour tenir compte de l'adhésion à l'Union européenne de la République de Croatie

Usually amendments to an international agreement (link - amendment)

(TI~Protocol amending) AND DTS_SUBDOM = INTER_AGREE AND DTT=A ORDER BY XC DESC

22015A0731(01)
22018A1220(01)
22018A0622(02)

Additional Protocol to the Trade Agreement between the European Union and its Member States, of the one part, and Colombia and Peru, of the other part, to take account of the accession of the Republic of Croatia to the European Union

Protocole additionnel à l'accord commercial entre l'Union européenne et ses États membres, d'une part, et la Colombie et le Pérou, d'autre part, en vue de tenir compte de l'adhésion de la République de Croatie à l'Union européenne

Usually amendments to an international agreement (link - amendment); or only a new protocol to be added to the agreement (link - addition)

(TI~Protocol additional) AND DTS_SUBDOM = INTER_AGREE AND DTT=A ORDER BY XC DESC

Legislative and non-legislative acts; complementary acts; celex sector 3 and 4

Complementary acts incl. Budget, ECB guidelines

32015B1623

Decision (EU, Euratom) 2015/1623 of the European Parliament of 29 April 2015 on the closure of the accounts of the general budget of the European Union for the financial year 2013, Section III — Commission

Décision (UE, Euratom) 2015/1623 du Parlement européen du 29 avril 2015 sur la clôture des comptes du budget général de l'Union européenne relatifs à l'exercice 2013, section III — Commission

TI~decision closure of the accounts of the general budget ORDER BY XC DESC

Legislative acts adopted by legislative procedure

Implementing, delegated and other acts not adopted by legislative procedure

32013A1218(02)
32013A1218(01)
32013A1217(02)

Council opinion of 10 December 2013 on the Economic Partnership Programme of the Netherlands

AVIS DU CONSEIL du 10 décembre 2013 concernant le programme de partenariat économique des Pays-Bas

Last published in 2013
Link to procedure
EP - Legislative observatory

There are some cases with Celex 5*XG (should be corrected?):

52002XG0221(01)
52001XG0410(02)
52001XG0410(04)

AU_CODED = CONSIL AND (DTS=3 AND DTT=A) ORDER BY XC DESC

32015A1031(01)
32019A0520(01)
32018A0911(01)

Commission Opinion of 29 October 2015 relating to the plan for the disposal of radioactive waste arising from decommissioning stages III and IV of the Bohunice A-1 Nuclear Power Plant, located in the Slovak Republic

Avis de la Commission du 29 octobre 2015 concernant le projet de rejet d’effluents radioactifs résultant des phases III et IV du déclassement du réacteur A-1 de la centrale nucléaire de Bohunice, en République slovaque

AU_CODED = COM AND (DTS=3 AND DTT=A) ORDER BY XC DESC

Commission proposals and related documents coming from legislative procedure; drafts

Preparatory acts from other EU bodies

52019XX0603(01)
52019XX0603(02)
52019XX0416(01)

Summary of the Opinion of the European Data Protection Supervisor on the proposal for a Regulation on ECRIS-TCN

Résumé de l’avis du contrôleur européen de la protection des données sur la proposition de règlement relatif au système ECRIS-TCN

Link to procedure + EP - Legislative observatory

TI~Summary of the Opinion of the European Data Protection Supervisor ORDER BY XC DESC

Commission proposals, drafts, other preparatory documents as well as Commission reports and working documents (green and white papers, communications, impact assesments, evaluations, fittness checks, etc.)

52013XC0806(02)

Draft Commission Regulation (EU) No …/… of 5 August 2013 amending Regulation (EC) No 1857/2006 as regards its period of application

Projet de règlement (UE) n ° …/… de la Commission du 5 août 2013 modifiant le règlement (CE) n ° 1857/2006 en ce qui concerne sa durée d’application

Not containing COM or SEC/SWD number
Not containing "Codified version" in the title
Those are drafts published in the OJ in the past

31998Y0307(02)

Draft Commission Directive amending Directive 90/388/EEC in order to ensure that telecommunications networks and cable TV networks owned by a single operator are separate legal entities

Projet de directive de la Commission modifiant la directive 90/388/CEE en vue de garantir que les réseaux de télécommunications et les réseaux câblés de télévision appartenant à un seul et même opérateur constituent des entités juridiques distinctes

Not containing COM or SEC/SWD number
Not containing "Codified version" in the title
Those are drafts published in the OJ in the past

31999Y0626(02)
C1995/291/06
31997Y1203(01)

Draft communication to operators in the banana sector - Subject: Applications for the registration of operators for 2000

Projet de communication aux opérateurs du secteur de la banane - Objet: demandes d'enregistrement des opérateurs pour l'an 2000

Not containing COM or SEC/SWD number
Those are drafts published in the OJ in the past

JOC_1990_044_R_0014_01

Draft joint declaration by the ACP States and the Community and its Member States

Projet de déclaration conjointe, des États ACP, de la Communauté et de ses États membres

Not containing COM or SWD (SEC) number
Those are drafts published in the OJ in the past

52019PC0038
52019PC0208

52015PC0487: Proposal for a COUNCIL REGULATION amending Regulation (EU) No 2015/104 as regards certain fishing opportunities

COM/2015/0487 final - 2015/0236 (NLE)

52015PC0487: Proposition de RÈGLEMENT DU CONSEIL modifiant le règlement (UE) 2015/104 en ce qui concerne certaines possibilités de pêche

COM/2015/0487 final - 2015/0236 (NLE)

Proposal for an amending regulation - "amending" must follow directly after type and author of proposed act

Link to procedure + EP - Legislative observatory

52019PC0088

Proposal for a REGULATION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL on certain aspects of railway safety and connectivity with regard to the withdrawal of the United Kingdom of Great Britain and Northern Ireland from the Union

COM/2019/88 final

Proposition de RÈGLEMENT DU PARLEMENT EUROPÉEN ET DU CONSEIL concernant certains aspects de la sécurité et de la connectivité du transport ferroviaire eu égard au retrait du Royaume-Uni de Grande-Bretagne et d’Irlande du Nord de l’Union

COM/2019/88 final

Proposal for not amending regulation

Link to procedure + EP - Legislative observatory

52015PC0049

Amended proposal for a REGULATION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL laying down Union procedures in the field of the common commercial policy in order to ensure the exercise of the Union’s rights under international trade rules, in particular those established under the auspices of the World Trade Organization (codification)

/* COM/2015/049 final - 2014/0174 (COD) */

Proposition modifiée de RÈGLEMENT DU PARLEMENT EUROPÉEN ET DU CONSEIL arrêtant des procédures de l’Union en matière de politique commerciale commune en vue d'assurer l'exercice par l’Union des droits qui lui sont conférés par les règles du commerce international, en particulier celles instituées sous l'égide de l'Organisation mondiale du commerce (OMC) (texte codifié)
/* COM/2015/049 final - 2014/0174 (COD) *

Link to procedure + EP - Legislative observatory

There might be a proposal with 2+ subsequent amendments:
52016PC0408 - 52015PC0350 - 52014PC0343 - how EV should be treated? There are 3 pending proposals, but only 1 act will be adopted - statistics

52013PC0932

Proposal for a DIRECTIVE OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL on port reception facilities for the delivery of waste from ships, repealing Directive 2000/59/EC and amending Directive 2009/16/EC and Directive 2010/65/EU

COM/2018/033 final - 2018/012 (COD)

Proposition de DIRECTIVE DU PARLEMENT EUROPÉEN ET DU CONSEIL relative aux installations de réception portuaires pour le dépôt des déchets des navires, abrogeant la directive 2000/59/CE et modifiant la directive 2009/16/CE et la directive 2010/65/UE

COM/2018/033 final - 2018/012 (COD)

Proposal for not amending directive
Link to procedure + EP - Legislative observatory

52017PC0637

Amended proposal for a DIRECTIVE OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL on certain aspects concerning contracts for the online and other distance sales of goods, amending Regulation (EC) No 2006/2004 of the European Parliament and of the Council and Directive 2009/22/EC of the European Parliament and of the Council and repealing Directive 1999/44/EC of the European Parliament and of the Council

COM/2017/0637 final - 2015/0288 (COD)

Proposition modifiée de DIRECTIVE DU PARLEMENT EUROPÉEN ET DU CONSEIL on certain aspects concerning contracts for the online and other distance sales of goods, amending Regulation (EC) No 2006/2004 of the European Parliament and of the Council and Directive 2009/22/EC of the European Parliament and of the Council and repealing Directive 1999/44/EC of the European Parliament and of the Council

COM/2017/0637 final - 2015/0288 (COD)

Link to procedure + EP - Legislative observatory

52016XC0430(01)

Withdrawal of Commission Proposals

RETRAIT DE PROPOSITIONS DE LA COMMISSION

Council positions, Statements of Council's reasons, etc.

52016AG0004(02)
52015AG0010(02)

52016AG0004(02): Statement of Council’s reasons: Position (EU) No 4/2016 of the Council at first reading with a view to the adoption of a Regulation of the European Parliament and of the Council on transmissible animal diseases and amending and repealing certain acts in the area of animal health (‘Animal Health Law’)

52016AG0004(02): Exposé des motifs du Conseil: Position (UE) no 4/2016 du Conseil en première lecture en vue de l'adoption du règlement du Parlement européen et du Conseil relatif aux maladies animales transmissibles et modifiant et abrogeant certains actes dans le domaine de la santé animale («législation sur la santé animale»)

52018AG0001(01)
52017AG0006(01)

52015AG0016(01): Position (EU) No 16/2015 of the Council at first reading with a view to the adoption of a Directive of the European Parliament and of the Council to approximate the laws of the Member States relating to trade marks Adopted by the Council on 10 November 2015 (Text with EEA relevance)

52015AG0016(01): Position (EU) No 16/2015 of the Council at first reading with a view to the adoption of a Directive of the European Parliament and of the Council to approximate the laws of the Member States relating to trade marks Adopted by the Council on 10 November 2015 (Text with EEA relevance)

Celex number contains split (01)
Link to procedure + EP - Legislative observatory

DN="5*AG*(01)" ORDER BY XC DESC

52018AG0001(02)
52017AG0006(02)

Statement of Council’s reasons: Position (EU) No 4/2016 of the Council at first reading with a view to the adoption of a Regulation of the European Parliament and of the Council on transmissible animal diseases and amending and repealing certain acts in the area of animal health (‘Animal Health Law’)

Exposé des motifs du Conseil: Position (UE) no 4/2016 du Conseil en première lecture en vue de l'adoption du règlement du Parlement européen et du Conseil relatif aux maladies animales transmissibles et modifiant et abrogeant certains actes dans le domaine de la santé animale («législation sur la santé animale»)

Celex number contains split (02)
Link to procedure + EP - Legislative observatory


DN="5*AG*(02)" ORDER BY XC DESC

CoR opinions

ECB opinions

EESC opinions

52016AE0137
52014AE4791

52014AE4791: Opinion of the European Economic and Social Committee on ‘European immigration policies’ (exploratory opinion)

52014AE4791: Avis du Comité économique et social européen sur les politiques européennes d'immigration (avis exploratoire)

52015AE6292

52015AE6292: Opinion of the European Economic and Social Committee on the ‘Proposal for a directive of the European Parliament and of the Council on certain aspects concerning contracts for the supply of digital content’ (COM(2015) 634 final — 2015/0287 (COD)) and the ‘Proposal for a directive of the European Parliament and of the Council on certain aspects concerning contracts for the online and other distance sales of goods’ (COM(2015) 635 final — 2015/0288 (COD))

52015AE6292: Avis du Comité économique et social européen sur la «Proposition de directive du Parlement européen et du Conseil concernant certains aspects des contrats de fourniture de contenu numérique»
[COM(2015) 634 final — 2015/0287 (COD))
et la
«Proposition de directive du Parlement européen et du Conseil concernant certains aspects des contrats de ventes en ligne et de toute autre vente à distance de biens»
[COM(2015) 635 final — 2015/0288 (COD))

Amendments to the proposal are described in the text - usually under "Specifric comments". There is a reference to a specific part of the proposal and description what should be changed.

There is link to procedure + European Parliament - Legisltive obsetvatory.

Example (52015AE6292):

4.2.5.1 Article 1 — Subject matter and scope
Procurement of certain online and distance services, such as leasing, should not be excluded from the subject matter and scope.

4.2.5.2 Article 2 — Definitions
1. The concept of commercial guarantee should also cover other forms of compensation, otherwise they will not be deemed to be covered by the rules in Article 15.

2. The concept of a tangible movable good has not been positively defined, which gives rise to different interpretations by Member States.
(...)

4.2.5.3 Article 3 — Level of harmonisation
The level of harmonisation should be minimum, with all the necessary consequences for the regime.

52015AE1246
52016AE1268

52015AE1246: Opinion of the European Economic and Social Committee on the ‘Proposal for a Regulation of the European Parliament and of the Council amending Regulation (EU) No 1304/2013 of the European Parliament and of the Council on the European Social Fund, as regards an increase of the initial pre-financing amount paid to operational programmes supported by the Youth Employment Initiative’ (COM(2015) 46 final)

52015AE1246: Avis du Comité économique et social européen sur la «Proposition de règlement du Parlement européen et du Conseil modifiant le règlement (UE) no 1304/2013 du Parlement européen et du Conseil relatif au Fonds social européen afin d’augmenter le montant du préfinancement initial versé aux programmes opérationnels soutenus par l’initiative pour l’emploi des jeunes» [COM(2015) 46 final)

Opinion not proposing amendment - in the opinion, no changes of specific parts of proposal are listed

52015IE1360
52014IE1468

52014IE1468: Opinion of the European Economic and Social Committee on ‘Completing EMU — The role of taxation policy’ (Own-initiative opinion)

52014IE1468: Avis du Comité économique et social européen sur le thème «Achever l’Union économique et monétaire — le rôle de la politique fiscale» (avis d’initiative)

52013IE6537
52012IE2321

52013IE6537: Opinion of the European Economic and Social Committee on ‘The Single Market Act — identifying missing measures’ (additional opinion)

52013IE6537: Avis du Comité économique et social européen sur «L'Acte pour le marché unique – Déterminer les mesures manquantes» (supplément d'avis)

EP resolutions, opinions, reports

Case law from Court of Justice of the EU and judicial informations published in OJ; celex sector 6

62015CA0058

Case C-58/15: Judgment of the Court (Sixth Chamber) of 23 December 2015 (request for a preliminary ruling from the Bayerischer Verwaltungsgerichtshof — Germany) — Firma Theodor Pfister v Landkreis Main-Spessart (Reference for a preliminary ruling — Agriculture — Health inspections — Official feed and food controls — Financing of controls — Inspection costs relating to slaughter — Regulation (EC) No 882/2004 — Directive 85/73/EEC — Possibility of levying fees covering the actual cost of inspection, exceeding the fees set by that directive)

Affaire C-580/14: Ordonnance de la Cour (sixième chambre) du 17 décembre 2015 (demande de décision préjudicielle du Verwaltungsgericht Berlin — Allemagne) — Sandra Bitter, en qualité de mandataire liquidateur de Ziegelwerk Höxter GmbH/Bundesrepublik Deutschland (Renvoi préjudiciel — Directive 2003/87/CE — Système d'échange de quotas d'émission de gaz à effet de serre — Amende sur les émissions excédentaires — Proportionnalité»)

judicial infomation EU case law - Court of Justice

62018CB0373

Case C-373/18: Order of the Court (First Chamber) of 31 January 2019 (request for a preliminary ruling from the Tribunal Administrativo e Fiscal de Penafiel — Portugal) — Prosa — Produtos e Serviços Agrícolas v Autoridade Tributária e Aduaneira (Reference for a preliminary ruling — Article 99 of the Rules of Procedure of the Court of Justice — Indirect taxes on the raising of capital — Directive 69/335/EEC — Articles 4 and 7 — Incorporation of a capital company — Stamp duty in force on 1 July 1984 — Subsequent abolition of that stamp duty, followed by its reintroduction)

Affaire C-373/18: Ordonnance de la Cour (première chambre) du 31 janvier 2019 (demande de décision préjudicielle du Tribunal Administrativo e Fiscal de Penafiel — Portugal) — Prosa — Produtos e Serviços Agrícolas/Autoridade Tributária e Aduaneira (Renvoi préjudiciel — Article 99 du règlement de procédure de la Cour — Impôts indirects frappant les rassemblements de capitaux — Directive 69/335/CEE — Articles 4 et 7 — Constitution d’une société de capitaux — Droit de timbre en vigueur au 1er juillet 1984 — Suppression de ce droit de timbre par la suite, puis réintroduction de celui-ci)

judicial infomation EU case law - Court of Justice

EFTA and EEA documents; celex sector E